How Lift works
Four steps. Same intake layer. Destination-specific output, with review kept where the firm or finance team already works.
Set up the destination route
Lift does not replace your ERP or force one output model. Xero routes are usually connection-led, while Business Central routes are configured around the tenant, company, vendors, dimensions, VAT or tax setup, approvals, and attachments expected in that environment. Import-led or bespoke routes can be configured around the agreed output file or handoff.
Use one folder per client
Clients and teams drop files into the agreed client folder whenever they have them. Lift watches those folders in the background, so the client and firm do not need to be online at the same time.
Accounting work is prepared
Lift reads the document, applies the configured client context, handles multi-page, multi-language, and multi-currency cases, then prepares the output the route needs: Xero draft, configured Business Central workflow output, structured Excel file, or another agreed route.
Review or submit through the agreed route
Your team can review where they already work. Direct submission should only be enabled where the route, controls and destination workflow support it.
Where to go next
Start with the product overview for the full buyer view, or jump into the route that matches your current workflow: shared folders, Xero, Business Central, SharePoint, or structured Excel imports.
For the control model behind step four, read the guide to review-first automation controls. To test the workflow, use one client or company, one intake route and a representative batch of supplier documents.
What a pilot should prove
The first pilot should show whether Lift reduces preparation work without weakening review. Use real supplier documents, include the awkward cases that slow the team down, and compare the prepared output against the firm's normal standard for supplier, totals, VAT or tax treatment, account coding, attachment and exception handling.
If the route works, expand deliberately: another client, another intake location, or another accounting destination. That keeps the workflow grounded in reviewed output instead of broad assumptions about automation.