Read accounting documents
Use the OData service, another agreed API or file interface available in the specific BAS configuration. Select documents for the required period and status.
Illustrative use case
Send documents from BAS to M.E.Doc
Prepare documents in BAS, check their details and send them to M.E.Doc through a configured connection. Data Bridge also helps retrieve their processing status so your accounting team can see the outcome.
BASM.E.Doc REST APIUBC Data Bridge Agent
HOW THE WORKFLOW RUNS
BASM.E.Doc REST APIUBC Data Bridge Agent
01Read accounting documents
02Prepare document fields
03Transfer through the API
04Retrieve processing status
THE CHALLENGE
What slows the work down
A document already exists in the accounting system, yet its fields must be entered again or transferred into the document-exchange application. The accountant then separately checks whether the transfer completed and what happened to the document. Missing fields and different templates complicate the process.
Accounting departments, BAS administrators and electronic-document integration specialists.A PRACTICAL EXAMPLE
Illustrative scenario: a company transfers prepared invoices or service documents from an available BAS interface to the M.E.Doc REST API. The workflow checks agreed fields, builds the required template structure and retrieves processing status for an internal register.
HOW THE WORKFLOW RUNS
From the first step to the right action.
Prepare document fields
Map counterparties, dates, amounts and line items to the expected structure. Validate required fields and template rules before the document is transferred.
Transfer through the API
Send prepared data to the configured M.E.Doc REST API with the required permissions. Retain the returned identifier for subsequent matching and operational checks.
Retrieve processing status
Use an authorised status method and match the response to its source document. Update an internal register or prepare a notification for the responsible accountant.
VALUE FOR THE TEAM
Make the work repeatable.
- Document data passes defined validation checks before it reaches the electronic-document application.
- Accountants and integrators can review the same mapping of source fields and target templates.
- A link between the source document and returned identifier provides a practical basis for reconciliation.
Keep control of the result.
- Confirm modules, licences, available methods and permissions in the particular BAS and M.E.Doc installations.
- Agree document keys and repeated-transfer behaviour so retries do not unintentionally create duplicate documents.
- Perform signing, onward transmission and regulated actions only within separately configured permissions and processes.
THE WORKFLOW OUTCOME
Document exchange gains an explicit route with validation and status checks, while accounting can review the result in an agreed working register.
Capabilities behind this workflowFROM IDEA TO WORKING FLOW
Bring your challenge. See a way forward.
Sources, rules and outcomes — let’s build the conversation around your workflow.