Does the automation send invoices to our customers?+
The described workflow creates draft invoices with journey PDF attachments. Your team reviews and approves the draft and supporting detail before anything is sent. Invoice preparation does not remove your accounts team’s responsibility for the final checks.
Where does the journey data come from?+
That is confirmed in the compatibility review. We inspect the source, format and fields available from your taxi-office process and agree what can be used. We do not assume every dispatch system or export can connect to the workflow.
What is included in the journey PDF?+
The PDF contains the agreed journey detail supporting the invoice. Its exact fields and layout depend on the data available and your requirements, so we agree and test them during setup rather than promise a universal template.
What if an account reference or journey record is wrong?+
Missing data, uncertain account mapping and other exceptions need human review under the agreed process. Your team checks the source records, draft invoice and PDF before approval. Automation does not establish that the underlying records are correct.
Does this include payment collection or bank reconciliation?+
Those are separate accounting processes and are not included in the draft invoice and journey PDF workflow described here. Tell us what you need during the consultation so any additional requirements can be scoped and priced separately.
Do we need to leave a computer running?+
No. This is a centrally hosted, managed EBA service. We agree the data connection, Xero access permissions and operational requirements first, with your accounts team retaining responsibility for reviewing and approving the output.