Uploading your first documents
Once your company is created — and, where applicable, your FEC imported — you can start uploading your documents. This is Simon’s basic gesture: you provide the document, it takes care of reading it, classifying it and bringing it into the accounting cycle.
Uploading a document
Drag a PDF into the application, or simply ask the agent to take care of it:
“I uploaded my January invoices into the inbox”
“Process the February BNP bank statement”
A file can contain several documents — a six-page statement followed by an invoice, for example. No need to separate them yourself: Simon detects them and processes them independently.
The recognized types
Simon supports seven families of documents, and knows what to extract from each:
| Type | Examples | What Simon extracts |
|---|---|---|
| Invoice | Supplier, customer, credit note | Net/VAT/gross amounts, third party, dates, lines, category |
| Bank statement | PDF or CSV | IBAN, operations (date, label, amount, direction), balances |
| Expense report | Tickets, receipts | Amount, issuer, category, fuel/meal details |
| Payslip | Pay slip | Gross, contributions, taxable net, net to pay |
| Tax notice | Tax, CFE, URSSAF | Type of tax, amount, deadline, taxable base |
| Commitment | Loan, leasing, contract | Schedule, rate, duration, principal/interest |
| OD | AGM minutes, provisions, adjustments | Type of manual journal entry, balanced accounting lines |
What happens on upload
You have nothing to orchestrate: uploading a document triggers an automatic chain. A sub-agent reads the file and cuts it into typed segments, each segment is annotated by the procedure suited to its type, then the extracted data is checked and the document enters the workflow. Identical files are discarded along the way thanks to their SHA256 fingerprint.
If a check fails, the document is not lost: it is put on hold with a block code that says precisely what to correct. The detail of this mechanism is described in Document ingestion.
And then?
A successful upload brings each document into the lifecycle. From there, the workflow moves it forward on its own as long as the prerequisites are met: extraction and validation of the data, then qualification (deductibility, VAT), bank reconciliation, and finally posting — the proposed journal entry then awaiting your approval.
The most common blocks
On upload, you will mainly encounter these situations:
| Block | Type | Cause | What to do |
|---|---|---|---|
| Incomplete extraction | hard | Extracted data not compliant | Correct the extracted fields |
| Inconsistent VAT | hard | Net + VAT ≠ gross | Correct the amounts |
| Wrong statement balance | hard | Balance inconsistent with the operations | Check the operations |
| Missing third party | hard | Third party not identified | Create or associate the third party |
| Probable duplicate | soft | File very close to an existing one | Confirm or dismiss |
| Direction to specify | soft | Supplier or customer invoice? | Specify the direction |