Your workflow in focus
Automate invoice intake: from document to reviewed filing
Connect email and PDF intake, extraction, entity assignment and review in an agreed workflow with SharePoint export.
Discuss an invoice-intake pilotWho this workflow is for
For accounting and operations teams capturing and reviewing invoices for multiple entities.
The everyday challenge
A shared mailbox does not establish responsibility for an invoice. Unclear entity assignments, missing fields and inconsistent filing create follow-up questions. A defined intake process with confirmed assignment and accountable review makes the next processing step visible and establishes a basis for document filing.
A concrete workflow example
Fictional example: three documents in a shared mailbox
A team processes PDF invoices for two entities. It confirms extracted fields and resolves exceptions before exporting originals and metadata.
| Document | Review case | Next step |
|---|---|---|
| Invoice A | Entity clear, fields confirmed | Review approved SharePoint export |
| Invoice B | Two possible entities | Have accountable person confirm assignment |
| Invoice C | Required field missing | Assign follow-up and complete the document |
Fictional documents, not customer results. Completed review or filing is not proof of payment. The exact module and installation scope is confirmed in the pilot.
How the workflow takes shape
Select a pilot intake
Start with an agreed mailbox or PDF intake and representative documents, including typical exceptions.
Define assignment and review
Specify entity rules, required fields, roles and the person confirming uncertain extraction or assignment.
Process documents and resolve exceptions
Review extraction and entity assignment. Route follow-up questions to the appropriate person and confirm fields before filing.
Validate filing and handoff
Check originals, metadata and the SharePoint destination path. Test module-dependent accounting connectors where applicable and record corrections in the pilot.
What we need to get started
- Suitable access to the agreed intake and SharePoint, plus representative test documents.
- Confirmed entity and role rules, review responsibilities and validated path mapping for your filing structure.
- Agree modules, licences, permissions and accounting interfaces specifically for the pilot.
What to know before you start
- The documented foundation covers intake, extraction, assignment, review, roles, SharePoint export and module-dependent accounting connectors; the actual installation state is checked.
- SharePoint export is one-way. Manual SharePoint changes are not synchronized back automatically.
- The documented banking module covers connections, selected accounts and account status, with no transfers or transaction reconciliation.
- The extended payment and filing workflow, S-Firm handoff and payment feedback are developments requiring separate validation. Document approval and payment authorisation remain separate decisions.
Common questions about this workflow
What happens when entity assignment is uncertain?
Define a review step and an accountable role. Use representative documents in the pilot to check how uncertain assignments are identified and confirmed.
Can we use our existing SharePoint structure?
Export is documented. Your folder and naming rules require explicitly validated path mapping and suitable permissions.
Does LISA pay approved invoices?
The documented banking module does not execute payments or reconcile transactions. A possible S-Firm handoff is validated separately and does not replace payment authorisation.
How do we start?
Bring a defined intake, sample documents, entity rules and desired filing structure. Agree modules, interfaces and review steps in the pilot discussion.
Make the next step concrete
Bring your current workflow and a typical example. Together, we clarify which data, systems and responsibilities matter for getting started.
Discuss an invoice-intake pilot