Accounting documents by email
Bring supported documents into the accounting workflow through configured email intake, reducing the need to download and manually re-upload every supplier attachment.
An intake channel for the documents already arriving
Many accounting tasks begin in an inbox. Configure the company's email intake and permitted sender information, then submit documents through the supported channel. The document enters the same classification and processing workflow as a supported upload, helping the team avoid a separate manual handling routine for every attachment.
Separate accounting intake from support requests
Use document intake for files that should become accounting work, with the right company context and instructions. Product questions or account problems belong in the appropriate contact or in-app support workflow. Review processing results rather than assuming that sending an email proves a document was recognized, recorded or accepted by an e-invoicing service.
What to know before you start
Email intake must be configured before use. Sender recognition, supported files and company access still apply; it is not unrestricted access to every employee's mailbox.
Practical questions
Does sending an email guarantee a posted transaction?
No. Check the processing outcome and any review request. Delivery and successful accounting processing are separate events.
Should support questions go to the document intake?
Use the in-app support workflow for an existing account issue, and the public contact page for product and onboarding questions.
Continue the workflow
AI invoice and receipt processing
Turn supported invoice, bill and receipt files into an accounting workflow with document extraction, record matching and the original attachment kept with the result.
Proactive accounting workflows
Configure remembered instructions and supported background activities so recurring accounting work can continue without repeating the same request every time.
Structured operational forms
Work directly with searchable records, contextual product choices, linked documents and workflow controls when a structured screen is better than a chat reply.