Bring incoming documents together
Combine invoices received by email through IMAP or Microsoft Graph with PDF uploads in a shared processing flow.
LISA · DOCUMENT ORGANIZATION & AUTOMATION
Organize documents. Clarify responsibilities. Understand the next step.
LISA connects incoming invoices, entity assignment, review and document filing. Further development brings payment status, processing and handoffs together in a traceable workflow, simplifying routine work while keeping decisions with the responsible people.
For accounting, finance teams and organizations handling multiple legal entities.
Documented product foundation · Workflow automation under development · Validate scope in a pilot
A shared foundation for your documents.
The documented modules connect intake, data processing and handoff. Configuration, licensing and pilot validation determine which modules are suitable for your environment.
Review data rather than retype it
Extract document data, check required fields and amounts, and make uncertain or failed results visible for review.
Assign documents to the right entity
Assign documents to a legal entity and review unclear matches. Entity-specific permissions support separate workspaces.
Respect responsibilities
Use roles and review approvals in the processing workflow. Approving a document and authorizing a payment are separate decisions.
File originals alongside their data
Export original documents and metadata to SharePoint. The documented export is one-way; manual SharePoint changes are not synchronized back automatically.
Connect the accounting workflow
Hand off documents using entity-specific accounting connectors. Availability depends on enabled modules and the actual configuration.
Development makes the complete process easier to follow.
These workflow capabilities are planned development scope. They will be tested incrementally against real processes and are not offered as fully available features.
Keep payment status separate
Distinguish already paid, still to pay and unclear. Processing, approval, filing and payment remain separate information.
Define naming and filing rules
Use confirmed fields for filenames and entity/year/month paths. Keep payer, processor and approver distinct.
Trace duplicates and changes
Review repeated arrivals and link original name, target name, action and time. Clarification cases receive ownership and a follow-up date.
Extend banking with controls
Validate S-Firm handoff and the assignment of returned status in practice. Preparing or recording an instruction does not prove payment.
Processed does not automatically mean paid.
The documented banking module covers connections, selected accounts and account status. It does not include transfers, payment execution or transaction reconciliation. S-Firm integration and payment feedback are separate extensions that require validation.
What your pilot needs
Start with an agreed mailbox or PDF intake, representative documents, entity rules and review responsibilities. SharePoint export and accounting connectors require appropriate licences, permissions and configuration. The pilot defines which modules and workflows are included.
Start with a manageable workflow.
- 01
Understand the process
Review intake channels, entities, roles and typical documents together.
- 02
Agree the rules
Confirm naming conventions, month selection, filing paths and responsibilities.
- 03
Validate routine work
Test assignment, review and filing with examples. Deliberately check errors and repeated arrivals.
- 04
Extend with controls
Add banking handoff and feedback after technical validation. Measure manual actions, waiting time and corrections in the pilot.
Before getting started
What is documented today and what is being developed?
The product foundation covers email/PDF intake, extraction, entity assignment, review, roles, SharePoint export and module-dependent accounting connectors. The extended payment and filing workflow is under development. The actual installation state is validated before use.
Does LISA execute payments automatically?
The documented banking module does not make transfers or reconcile transactions. Controlled S-Firm handoff is an integration option requiring validation. Payment permissions and authorization are agreed separately.
Will LISA fit our SharePoint structure?
SharePoint export is documented. Existing entity/year/month folders and custom naming rules require an explicitly validated path mapping. One-way export does not synchronize SharePoint changes back.
What prerequisites do we need?
Suitable access to the intended mailboxes, SharePoint and any accounting systems is needed, together with agreed entity and role rules. Modules, licensing, interfaces and requirements are clarified for the pilot.
How are benefits and terms agreed?
We define pilot scope and success criteria using your documents and workflow. Processing time, questions and corrections are measured; fixed savings are not promised. Implementation, licensing and support are agreed individually.
Which document workflow creates unnecessary manual work for your team?
Bring a typical process. Together we define the right starting point, review your systems and identify the next useful automation steps.
Discuss a pilot