Strategy
M&A, capital markets, and strategic advisory for transformative deals.
View all StrategyData rooms and transactions. The analysis and the recommendation are signed by the people on the team.
Discover BMC One Strategy Log in to BMC OneFree first meetingBy video call
Tax
Structuring, planning, and compliance across jurisdictions.
View all TaxForms 720 and 721
Filing period from 1 January to 31 MarchForms 720 and 721
The filing period ends on 31 MarchTax authorities, deadlines and powers of attorney. Our team prepares, files and responds.
Discover BMC One Tax Log in to BMC OneFree first meetingBy video call
Legal
End-to-end legal counsel to protect and advance your business interests.
View all LegalSignatures, case files and deadlines. A BMC team handles every matter, with in-house legal counsel on the legal side; in BMC One you see its phases and the status of each one.
Discover BMC One Legal Log in to BMC OneFree first meetingBy video call
Operations
Outsourced finance, people, and governance so you can focus on growth.
View all OperationsAccounting, invoices, bank statements and payroll. Our team books, calculates and submits.
Discover BMC One Business Services Log in to BMC OneFree first meetingBy video call
New guides on the latest Spanish tax and immigration developments.
Practical tools for informed decision-making.
Everything BMC One does
Each capability links to its area. Partial: part of it works; the detail is on the area page.
Try
Business Services
Tax
Legal
Security
Nothing for “”. Try “VAT”, “payroll”, or “signature”.
By area
Business ServicesOperations
Your business, up to date in one place
Our team books, calculates and submits.
Ask your assistantExamples
How many active employees do we have, and under which collective agreement and type of contract?
Add these three employees with their DNI, Social Security number and start dateThey stay in BMC One; nothing is notified to Social Security.
Tax
Every Spanish tax deadline, in plain sight
Our team prepares, files and responds.
Ask your assistantExamples
Which returns do we have this quarter and which have already been filed?
Change the tax address on the record to Calle Muestra 5, MadridIt changes the record in BMC One; nothing changes with the AEAT.
Legal
Every phase, with its status and its date
A BMC team handles every matter, with in-house legal counsel on the legal side; in BMC One you see its phases and the status of each one.
Ask your assistantExamples
Which documents are still awaiting signature and who has yet to sign?
Prepare an envelope for Lucía Prueba to sign this contract on the last pageIt stays in draft. Sending it is a critical action: only with the Custom role.
Strategy
The whole transaction in one file
The analysis and the recommendation are signed by the people on the team.
Ask your assistantExamples
Find what BMC has written to us about the capital increase
Where do the tax obligations of every company in the group stand, and which one has gaps?With a group access.
Across all areas
ConnectionsAPI, MCP and webhooks
It works with any assistant that supports remote MCP connectors with OAuth sign-in; for example, Claude, which we have tested it with, or ChatGPT Business, Enterprise and Edu, as documented.
With a token, also Gemini CLI, Cursor, n8n, Make or Zapier; and, by API and signed webhooks, your own systems.
No assistant files with the AEAT, moves money or signs for you.
Only with the Custom role, chosen permission by permission.
API and MCPConnect your AIIntegrationsPublic administrations
Security
Its own scoped access, never your session
BMC One, its database and your documents are on our dedicated servers in Germany. The database is not exposed to the internet.
No assistant files with the AEAT, moves money or signs for you.
Illustration of what you choose when you authorise an access. Fictitious data.
Returns
ReturnsForms 720, 721 and 210
Returns for investors and non-residents
Assets held abroad, crypto assets and non-resident income, at two levels: Platform and With an adviser.
BMC's client environment, included in your engagement: never sold separately.
Developers
Received (purchase) invoices extracted by the docparser pipeline.
GET /suppliers List received (purchase) invoicesGET /suppliers/items/{id} Get one received invoiceGET /suppliers/items/{id}/file Download the original purchase documentPOST /ingest/batches Upload a purchase document for extraction/suppliersList received (purchase) invoices
Purchase invoices extracted by the docparser pipeline. Date filters apply to `createdAt` (ingestion date), not the extracted invoice date.
Required permission:
purchases:documents.read (Purchases › Supplier invoices and expenses › Read)
Pagination: Parameters page and limit. The response includes total, page, limit, hasMore.
| Name | In | Type | Description |
|---|---|---|---|
state | query | string | Ingestion pipeline state, e.g. BOOKED, NEEDS_REVIEW. |
needsReview | query | boolean | |
dateFrom | query | string (date) | |
dateTo | query | string (date) | |
page | query | integer | Default: 1 |
limit | query | integer | Default: 50 · maximum: 500 |
200 List of supplier invoices · application/json
| Name | Type | Description |
|---|---|---|
items | object[] | |
items[].id | string | |
items[].companyId | string | |
items[].filename | string | |
items[].confidence | numbernullable | |
items[].state | string | |
items[].needsReview | boolean | |
items[].createdAt | string (date-time) | |
items[].updatedAt | string (date-time) | |
total | integer | Total items matching the filter. |
page | integer | Page returned (starts at 1). |
limit | integer | Page size applied. |
hasMore | boolean | There are more pages after this one. |
401 Missing or invalid Bearer token. · application/json
| Name | Type | Description |
|---|---|---|
error | string | Human-readable error message |
required_permission | string | Present on 403 - the missing permission (area:resource.action) |
403 Token lacks the required permission, or the resource is outside the token's tenant. · application/json
| Name | Type | Description |
|---|---|---|
error | string | Human-readable error message |
required_permission | string | Present on 403 - the missing permission (area:resource.action) |
429 Rate limit exceeded. · application/json
| Name | Type | Description |
|---|---|---|
error | string | Human-readable error message |
required_permission | string | Present on 403 - the missing permission (area:resource.action) |
curl -X GET "https://app.bm.consulting/api/v1/suppliers?limit=50" \
-H "Authorization: Bearer $BMC_TOKEN" const res = await fetch("https://app.bm.consulting/api/v1/suppliers?limit=50", {
method: "GET",
headers: {
Authorization: `Bearer ${process.env.BMC_TOKEN}`,
},
});
if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);
const data = await res.json(); import os
import requests
res = requests.get(
"https://app.bm.consulting/api/v1/suppliers?limit=50",
headers={"Authorization": f"Bearer {os.environ['BMC_TOKEN']}"},
timeout=30,
)
res.raise_for_status()
data = res.json() /suppliers/items/{id}Get one received invoice
Full extracted detail including per-line fields. 404 for items outside your tenant.
Required permission:
purchases:documents.read (Purchases › Supplier invoices and expenses › Read)
Pagination: Not paginated: returns the full set.
| Name | In | Type | Description |
|---|---|---|---|
idrequired | path | string |
200 Supplier invoice · application/json
| Name | Type | Description |
|---|---|---|
id | string | |
companyId | string | |
filename | string | |
confidence | numbernullable | |
issuerNif | stringnullable | |
issuerName | stringnullable | |
invoiceNumber | stringnullable | |
invoiceDate | string (date) | |
dueDate | string (date)nullable | |
baseAmount | numbernullable | |
vatAmount | numbernullable | |
total | numbernullable | |
currency | string | |
state | string | |
lines | object[] | |
lines[].description | stringnullable | |
lines[].quantity | numbernullable | |
lines[].unitPrice | numbernullable | |
lines[].lineTotal | numbernullable | |
lines[].vatRate | numbernullable | |
lines[].taxCode | stringnullable | SII regime code |
lines[].accountCode | stringnullable | PGC account code |
fileUrl | string (uri) | Exchange for a presigned download via GET /suppliers/items/{id}/file. |
401 Missing or invalid Bearer token. · application/json
| Name | Type | Description |
|---|---|---|
error | string | Human-readable error message |
required_permission | string | Present on 403 - the missing permission (area:resource.action) |
403 Token lacks the required permission, or the resource is outside the token's tenant. · application/json
| Name | Type | Description |
|---|---|---|
error | string | Human-readable error message |
required_permission | string | Present on 403 - the missing permission (area:resource.action) |
404 Resource not found (or belongs to a different tenant). · application/json
| Name | Type | Description |
|---|---|---|
error | string | Human-readable error message |
required_permission | string | Present on 403 - the missing permission (area:resource.action) |
429 Rate limit exceeded. · application/json
| Name | Type | Description |
|---|---|---|
error | string | Human-readable error message |
required_permission | string | Present on 403 - the missing permission (area:resource.action) |
curl -X GET "https://app.bm.consulting/api/v1/suppliers/items/<id>" \
-H "Authorization: Bearer $BMC_TOKEN" const res = await fetch("https://app.bm.consulting/api/v1/suppliers/items/<id>", {
method: "GET",
headers: {
Authorization: `Bearer ${process.env.BMC_TOKEN}`,
},
});
if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);
const data = await res.json(); import os
import requests
res = requests.get(
"https://app.bm.consulting/api/v1/suppliers/items/<id>",
headers={"Authorization": f"Bearer {os.environ['BMC_TOKEN']}"},
timeout=30,
)
res.raise_for_status()
data = res.json() /suppliers/items/{id}/fileDownload the original purchase document
Returns a redirect to a short-lived presigned URL for the original file.
Required permission:
purchases:documents.read (Purchases › Supplier invoices and expenses › Read)
Pagination: Not paginated: returns the full set.
| Name | In | Type | Description |
|---|---|---|---|
idrequired | path | string |
302 Redirect to a presigned download URL
401 Missing or invalid Bearer token. · application/json
| Name | Type | Description |
|---|---|---|
error | string | Human-readable error message |
required_permission | string | Present on 403 - the missing permission (area:resource.action) |
403 Token lacks the required permission, or the resource is outside the token's tenant. · application/json
| Name | Type | Description |
|---|---|---|
error | string | Human-readable error message |
required_permission | string | Present on 403 - the missing permission (area:resource.action) |
404 Resource not found (or belongs to a different tenant). · application/json
| Name | Type | Description |
|---|---|---|
error | string | Human-readable error message |
required_permission | string | Present on 403 - the missing permission (area:resource.action) |
429 Rate limit exceeded. · application/json
| Name | Type | Description |
|---|---|---|
error | string | Human-readable error message |
required_permission | string | Present on 403 - the missing permission (area:resource.action) |
curl -X GET "https://app.bm.consulting/api/v1/suppliers/items/<id>/file" \
-H "Authorization: Bearer $BMC_TOKEN" const res = await fetch("https://app.bm.consulting/api/v1/suppliers/items/<id>/file", {
method: "GET",
headers: {
Authorization: `Bearer ${process.env.BMC_TOKEN}`,
},
});
if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);
const data = await res.json(); import os
import requests
res = requests.get(
"https://app.bm.consulting/api/v1/suppliers/items/<id>/file",
headers={"Authorization": f"Bearer {os.environ['BMC_TOKEN']}"},
timeout=30,
)
res.raise_for_status()
data = res.json() /ingest/batchesUpload a purchase document for extraction
Multipart upload of a purchase invoice (PDF/image). L1 dedup by SHA-256 returns 200 for an identical re-upload. `companyId` is forced from the token. Machine reading: with your own account-bound token, a document sent without `consent` is queued for OCR + extraction, unless your account asked for human review only; `consent=AI_AUTO` is read even then (your choice for that document wins); `consent=HUMAN_ONLY` is never read. Internal BMC tokens (BMC staff, agents, the MCP gateway) need an explicit `consent=AI_AUTO` or `origen=email`, and can never override your account's human-review-only preference. A document that is not read is stored and a person fills it in (`status: NEEDS_REVIEW`). The response never hides a non-read: `lectura: "en_cola"` when it is queued for reading, or `lectura: "no"` with `motivo` from a closed list: `sin_consentimiento` (internal token, no consent and no origen), `origen_sin_eleccion` (internal token, a channel other than email and no consent), `cuenta_solo_personas` (the account asked for human review only), `human_only` (consent=HUMAN_ONLY), `propietario_sin_resolver` (the owning account cannot be resolved: never read), `origen_no_verificado` (internal token, `origen=email` without a reference to an e-mail of the same account). `origen=email` counts only with `threadAttachmentId` or `messageId` of an e-mail of the same account. `consentimiento` carries the decision: consent, origen, llamante (cliente | interno) and origenVerificado.
Required permission:
documents:ingest.create (Documents › Document capture › Create)
Pagination: Not paginated: returns the full set.
multipart/form-data| Name | Type | Description |
|---|---|---|
filerequired | string (binary) | The document bytes. |
filename | string | |
consent | string | Whether the document may be read by machine. Your account-bound token: missing = read unless your account asked for human review only; AI_AUTO = read even then; HUMAN_ONLY = never read. Internal tokens: missing = not read unless origen=email. Values: AI_AUTO, HUMAN_ONLY |
origen | string | Channel the document came in through. Only decides for internal tokens: email is read unless the account asked for human review only, and only with the e-mail reference (threadAttachmentId or messageId); any other channel only with consent AI_AUTO. Values: email, subir, data_room, desconocido |
threadAttachmentId | string | With origen=email: the attachment of the source e-mail. It must exist and belong to the same account. |
messageId | string | With origen=email: the source e-mail message, if no threadAttachmentId. It must exist and belong to the same account. |
200 L1 dedup hit - identical file already ingested
201 File accepted (returns batchId + itemId, `lectura`, `motivo` and `consentimiento`): `status: QUEUED` and `lectura: "en_cola"` when it is read by machine; `status: NEEDS_REVIEW` and `lectura: "no"` with its `motivo` when a person fills it in
400 Missing file, unsupported type, or too large · application/json
| Name | Type | Description |
|---|---|---|
error | string | Human-readable error message |
required_permission | string | Present on 403 - the missing permission (area:resource.action) |
401 Missing or invalid Bearer token. · application/json
| Name | Type | Description |
|---|---|---|
error | string | Human-readable error message |
required_permission | string | Present on 403 - the missing permission (area:resource.action) |
403 Token lacks the required permission, or the resource is outside the token's tenant. · application/json
| Name | Type | Description |
|---|---|---|
error | string | Human-readable error message |
required_permission | string | Present on 403 - the missing permission (area:resource.action) |
429 Rate limit exceeded. · application/json
| Name | Type | Description |
|---|---|---|
error | string | Human-readable error message |
required_permission | string | Present on 403 - the missing permission (area:resource.action) |
curl -X POST "https://app.bm.consulting/api/v1/ingest/batches" \
-H "Authorization: Bearer $BMC_TOKEN" \
-F "file=@documento.pdf" import { readFile } from "node:fs/promises";
const form = new FormData();
form.append("file", new Blob([await readFile("documento.pdf")]), "documento.pdf");
const res = await fetch("https://app.bm.consulting/api/v1/ingest/batches", {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.BMC_TOKEN}`,
},
body: form,
});
if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);
const data = await res.json(); import os
import requests
res = requests.post(
"https://app.bm.consulting/api/v1/ingest/batches",
headers={"Authorization": f"Bearer {os.environ['BMC_TOKEN']}"},
files={"file": open("documento.pdf", "rb")},
timeout=30,
)
res.raise_for_status()
data = res.json() Reply by email · no commitment