Most finance tools keep documents in piles: invoices here, bank lines there. Likvid keeps events, and the documents are legs of them.
Card revenue is where an ordinary bank sync gives up. A processor pays out one lump sum; behind it are ninety-odd charges, its own fee, a refund and a dozen invoices — none of which is in the bank line.
Where the processor publishes them, Likvid reads the payout from the source and splits it back into its parts, each hanging off one event. A reversal or an advance invoice works the same way.
The Hungarian processors — SimplePay and Barion — publish no such listing. There the payout is recognised on the bank statement and kept open as one event until the processor's own report fills in the parts. We name that limit rather than let a diagram imply it away.
Invoice, bank movement, tax record, certificate and email attach to the same happening, each in its own role. That is why the chain survives a reversal or a part-payment.
An event with incomplete documents stays open, and you see how much money is sitting in it — an advance invoice that never got its final invoice is money you can still collect.
Payout gross → processor fee → refund → which invoice each charge belongs to. Every step keeps its trail: what created it, when, and on what evidence.
If a payment is a leg of an event, the absent invoice is a hole with a shape and an amount — not a vague feeling that something is off.
Any figure on any screen leads back to the system that said it and the document it came from. A figure with no traceable origin is not shown as fact.
Part-payments, reversals, a bank charge nested under the movement, foreign currency in its original amount, one card settlement split back to the invoices inside it.
Free during the beta, access by request. Connecting takes about fifteen minutes, and the bank side only ever reads.