Data and integrations

For a pilot, the only thing we strictly need is access to your actual invoices. PDFs are preferred, but Bardo also reads other common image formats. The person doing the data extraction gets access to a secure web-based dataroom where files upload directly into our Swedish-hosted Azure environment.

For a full delivery, we also recommend including your accounting metadata (how invoices are booked) so the inventory can be broken down by cost centre, result unit, or subsidiary. Bardo handles enrichment from there: cleaning up messy data from multiple sources, then structuring and mapping it for calculation workflows.

Read-only access to the data you already have:

• Accounts Payable metadata
• Purchase orders and supplier information
• Invoices and receipts (PDF, XML, EDI, image formats)
• Shipment and route data where applicable

No write-back capability. Your data stays securely within your approved environment. All processing excludes personally identifiable information, and customer data is never used for external model training.

Bardo's connects to your system through a secure dataroom.

Modern and easy to use. Upload ERP exports straight into the data room. No integration work required up front.

Quickly. A typical path is:

• Start with a sample export of 500 to 1,000 invoices to validate output quickly and save time and cost in early rollout. Most teams use this as their capability demo.
• Move to full recurring data upload of your company's transaction data.
• Deeper API integrations with your current systems.

This helps teams align scope, ownership, and rollout sequence before scaling.

Bardo only ingests fields required for activity mapping and audit. Bank details and personal identifiers are masked at ingestion. Field-level rules govern exports and APIs, with options to hide or pseudonymise sensitive information.