Skip to content

Document history

Every invoice, every bank statement and every cash receipt keeps its own log: who did what, when, with which tool, and what changed. That same log feeds an organization-wide view, reserved for administrators, of everything moving in the accounting.

Updated on September 11, 2026

What it is for

An accounting document passes through several hands: the person who enters it, the firm that reviews it, the assistant that prepares a draft, the automatic scan that reads the file, the reminder that leaves on its own. Without a log, only the final state remains, and the question “who changed that due date, and when?” has no answer. The history keeps every step, timestamped, from the most recent to the oldest.

Note

Nothing is erased. Deleting a draft does not erase its log: the entry stays, with the number and the amount of the document that is gone.

What is recorded

The four document families share one log. Each one records the events of its own life cycle.

  • Sales invoices and credit notes

    Draft creation, edit and deletion, issuing, email delivery, reminders, automatic reminder settings, payment and its reversal, cancellation and restoration, credit note creation, credit allocation and its release, accounting assignment, PDF regeneration, exchange rate backfill.

  • Purchase invoices

    Creation — manual entry, from a vault document, from the email intake address or from an import — edit, deletion, recording, reopening, correction request, rejection, resubmission, cancellation and restoration, payments added, edited or deleted, credit allocation, accounting assignment, linked file, automatic scan.

  • Bank statements

    Statement import as PDF, image or spreadsheet, automatic scan of the file, edit, bank account and file linking, confirmation, deletion.

  • Cash receipts

    Receipt scan or manual entry, automatic scan, edit, confirmation, deletion, linked file.

Note

An automatic scan writes its own thread: started, completed — with the number of recognized fields — failed or cancelled. So you can see why a document stayed a draft.

Who shows up as the author

Every entry carries its author. That author is not always a person.

  • Someone in your organization, with the name and email address they carry in your member list.
  • A member of your accounting firm, whose name is preceded by the firm's own: the action is recorded on behalf of the firm that performed it, inside its client's workspace.
  • Atlas, when the assistant creates or edits a document for you. The entry keeps the link to the exact tool call that produced it.
  • An organization API key, when an integration writes remotely. The entry names the key that was used, not only the person who created it.
  • An agent connected over MCP, meaning an external assistant allowed to write in your organization.
  • React Box itself, for whatever runs with nobody behind it: an automatic reminder sent on schedule, a regenerated PDF, an exchange rate filled in once the rate is published, a scan that stalled and was given up on.

What an edit records

An edit does not merely say that something was edited: it lists the fields it touched, with the value before and the value after. On a sales invoice, those are the issue date, the due date, the customer, the currency, the payment method, the payment terms, the notes, the footer and the VAT setting. On a purchase invoice, the supplier, its invoice number, the dates, the currency, the payment method, the paying account and the notes. On a statement, the bank account, the period dates, the balances and the label. On a receipt, the third party, the number, the date, the amount, the currency, the payment method and the reason.

Note

Invoice lines are never detailed in the log: the history states that they changed and how many remain, nothing more. And an edit that changes nothing — you open the document and save without touching anything — writes no entry at all.

The history of one document

It sits in the document's detail screen, below its information: sales invoice, purchase invoice, bank statement, cash receipt. Events are ordered from the most recent to the oldest and load in batches, a button at the bottom of the list asking for more. An edit entry expands to show the fields, before and after. On mobile, the same history sits at the bottom of every detail screen.

Note

The history follows the document's read permission: whoever can open the invoice can read its log. There is no separate setting.

The organization log

One screen answers the question “what moved in the accounting this week, and who moved it”. It gathers the four families into a single table — when, who, which action, which document — and every row opens the document it refers to. You will find it in the Accounting section, under History, on the web as on mobile.

Administrators only

The organization log is reserved for administrators and owners. It is not a checkbox inside a role: the role itself opens the screen. Other members keep the history of every document they are allowed to open.

Filtering the log

Five filters that combine, and a table that paginates.

  • The family

    Sales, purchases, bank statements or cash receipts.

  • The action

    Issuing, delivery, payment, cancellation, automatic scan: the full list is offered in a searchable field.

  • The author

    One person in particular, or an origin: Atlas, an API key, an MCP agent, the system.

  • The period

    A date range, picked in a single gesture.

  • The search

    A sales invoice number, a supplier's invoice number, a statement label or a receipt number.

The firm inside a client workspace

An accounting firm finds the same log inside each of its client workspaces, with the same filters. Everything one of its members does there is recorded on behalf of the firm: the client reads “Dupont Accounting · Marie” and knows the action came from outside their own organization.

Note

On the firm's side, a client's log opens to the members who see every client workspace, and to the supervisor assigned to that particular one.