Cut invoice admin in Business Central.

Take entry, coding and mapping off your team

Give reviewers the invoice information they need in the fields they use. Lift can prepare:

• Supplier/vendor details
• Document dates
• Due dates and payment details where present
• Currency and totals
• Line descriptions and amounts
• VAT/tax treatment suggestions
• Account and dimension suggestions for the agreed company setup
• Custom field mapping, including extension fields, as part of the implementation
• Source document attachment or reference
• Review status for unclear documents

Map the fields your business actually uses

Your reporting and processes may rely on more than standard invoice fields. Lift’s implementation can include custom field mapping alongside account and dimension mapping, including fields introduced by your Business Central extensions.

For example, a project reference from the source document can be mapped to the field your team uses, while department information is prepared for the relevant dimension. We work through where each value comes from and how it should be formatted, validated and delivered.

Your format, your destination

Lift’s preparation can be extended to fit the structure and destination your business needs. We can scope delivery through an API, a structured import file or another integration, including a workflow that sits alongside Business Central.

Bring us the result you want: which information should arrive, in what shape and where. Our team designs the transformation, field mapping and delivery around that process, with source evidence and review handling included in the scope.

An implementation built around your workflow

Business Central integrations are scoped projects. We establish the required fields, extensions, permissions, delivery method and review steps with your team, then agree the implementation scope and timing. Start with the workflow that would save the most preparation and expand from there.

The Business Central implementation checklist explains the details we work through together. You do not need to complete it before requesting a demo.

Review-first controls

Lift can support a review-first approach where prepared document data is checked before approval or posting. This is important for firms and finance teams that need control over VAT, dimensions, account treatment, period handling, and evidence. Read more about Lift's review-first controls for accounting workflows.

Business Central Payables Agent vs Lift

Both approaches prepare accounting information and involve reviewers. Microsoft’s Payables Agent works inside Business Central from a monitored mailbox. Consider Lift when folder intake, business-specific policies or preparation across multiple accounting systems match your process. Test representative invoices and total review effort before choosing.

Microsoft capabilities checked on 5 October 2026. Source: Microsoft’s Payables Agent overview. Availability and limits depend on Microsoft’s current release and your environment.

Good pilot candidates

Business Central pilots work best where the team can test a real intake route, real supplier documents, and a narrow review path. Good candidates include:

• Internal finance teams using Business Central
• Accounting firms with clients moving from Xero or desktop systems to Business Central
• Businesses with SharePoint-based document intake
• Teams with repetitive supplier invoice preparation
• Organisations where dimensions and VAT policy matter

This is also relevant when a firm is planning a client accounting system migration: Xero to Business Central and wants document intake to stay stable while the destination workflow changes.

Discuss the workflow, then scope a pilot

For Business Central workflows, a demo can establish fit before a scoped pilot: one company, one document intake route, one approval path, and a representative sample of supplier documents. That gives the implementation enough evidence to validate supplier matching, VAT or tax treatment, account and dimension suggestions, attachment behaviour, and unclear-file handling before broader rollout.