Our entities do not all work the same way. Does one queue still work?

Yes, because what differs is a setting rather than a process. A rule can be shared across every company or set for one of them, and the case says which one applied to it. The vocabulary of states is the same everywhere, which is what makes two companies comparable at all.

We are onboarding part of the group. What happens to the rest?

A counterpart outside the onboarded set is a state with a name on it, not a blank and not an error. It is shown on the status list, it is left out of the totals deliberately, and the label over each total says which companies it covers. Onboarding another company later is a configuration.

What does somebody need to know before they can work an item?

What is on the item. The movement or the row, the company that booked it, the checks that ran and what each one read, the ones that found nothing, and the specific thing that would settle it. That is the design goal: a case that can be worked without asking anybody.

Who can see which companies?

Access is by company and by role. A person sees the companies they work and the actions their role allows, and every action they take is recorded against them. A center serving several countries usually needs that split before it needs anything else.

What happens to an item nobody picks up?

It stays. It keeps its state, it keeps everything that was checked on it, and it never drops out of a count to make that count look better. If it is the kind of case that closes itself, the case says so, which is how the desk tells waiting apart from stuck.

For shared service centers

The same decision for every entity, by whoever is at the desk today.

A shared services desk runs on consistency it can hand over. The work arrives as a queue with a name on every case, the record that decided it, and the reason it is still open — so the person who picks it up did not have to be here last month.

Request a demo

Pending Review · across the group

Aug 14

Queues on this desk

Statement lines, ledger rows, movements and counterpart pairs. Four different units, so they are counted separately and never added together.

Statement lines waiting to be matched: 33
Ledger rows stopped on a named reason: 64
Movements the evidence named two parties on: 9
Counterpart pairs whose two sides disagree: 3

Companies in the onboarded set4

Each lane is worked in its own screen, and every case in it carries the company that booked it.

One case

What does an item in the queue arrive with?

Four things, and together they are the whole of what makes a queue something you can hand over. An item that does not carry them is an item somebody has to ask about, and the person they ask is the one who was here last month.

What it is, and whose books it sits in: The movement or the row itself, the company that booked it and the account it touches. Nothing arrives as a case number that has to be looked up somewhere else first.
What was already checked, and on which record: The checks that ran, in the order they ran, and the record each one read. The ones that found nothing are on the case too, because that is how a reader knows the question was asked at all.
What is missing: The specific thing that would settle it: a counterpart’s posting, a mapping for a ledger account, an identifier nobody holds, or a decision only a person can make.
What happens if nobody touches it: Whether it closes itself on tomorrow’s statement or waits for somebody. A timing difference and a mistake look identical in a list that does not say which is which.

That is the difference between a queue and an inbox. An inbox holds messages about work. A queue holds the work, with everything the next person needs already on it.

Where the rule lives

What can somebody pick up on their second day?

Anything, if the rule that settles a case is a property of the system rather than of the person running it. That is what makes a center portable, and it is the thing that quietly does not survive a handover.

The order the checks run in: Intercompany first, then the identifiers a record carries, then the bank account, then the payment itself. It is the same ladder for every company, and it lives where the work happens rather than in an induction deck.
The record that decided it: A case is settled by an identifier a record carries, never by two names looking alike. Which record decided it stays on the case, so the second person reads the reasoning instead of repeating it.
The cases nobody should decide: Where the evidence names two companies and nothing ranks them, the engine declines and leaves both on the case. A wrong counterparty is worse than an open one, and worse still when it was a guess made under pressure on a Friday.

Change how a case is settled and it applies to every company from that moment. Nobody re-explains it country by country, and no company is quietly running last year’s version of the rule because the person who knew it moved teams.

Consistency is not a policy in a document. It is what happens when the decision is made in one place, on records, for every company at once.

Every company on one list

Is entity three settled the same way as entity sixty-one?

The same two counts and the same state names, for every company the desk books for. And the companies whose ledgers nobody has handed over are still on the list, because a company missing from a status screen looks exactly like a company with nothing to report.

Reconciliation Status · by entity

Aug 14

Lines waiting for a person

Across the companies whose ledgers are inside the onboarded set.

Company	Matched	Waiting
Corporation Holding In the setMatched211Waiting3	211	3
Corporation España In the setMatched594Waiting18	594	18
Corporation Servicios In the setMatched174Waiting4	174	4
Corporation México In the setMatched272Waiting8	272	8
Corporation Patrimonial UnmanagedNo ledger in the set	No ledger in the set
Corporation Re UnmanagedNo ledger in the set	No ledger in the set

Lines read across the set1,284

Matched and waiting add to the lines read, per company and in total. The two unmanaged rows add to neither, and the label over the total says which companies it is over.

A group onboards a subset of its companies, and that is the normal shape rather than something to hide. What is not acceptable is a counterpart appearing as a blank: it gets a state of its own, it is left out of the totals on purpose, and the label over every total names the companies it covers.

When the work moves

What changes when a process moves to the center?

Not the headcount and not the calendar. What changes is what a case carries and where the rule that settles it lives.

The queue is the work: Everything waiting sits in one place, with what it is, which company booked it and what is missing. Nothing lives in a mailbox, and nothing is a case only because somebody remembers that it is.
A rule changes in one place: How a case is settled is a setting rather than a habit. Change it and every company follows it from that moment, including the ones nobody has looked at this week.
Handover is reading, not asking: The record of a decision travels with the case: the checks that ran, the record each one read, and the ones that found nothing. A new person reads the case instead of interviewing a colleague.

The modules a center runs on

What centers ask

The questions we get from a shared services lead

01Our entities do not all work the same way. Does one queue still work?: Yes, because what differs is a setting rather than a process. A rule can be shared across every company or set for one of them, and the case says which one applied to it. The vocabulary of states is the same everywhere, which is what makes two companies comparable at all.
02We are onboarding part of the group. What happens to the rest?: A counterpart outside the onboarded set is a state with a name on it, not a blank and not an error. It is shown on the status list, it is left out of the totals deliberately, and the label over each total says which companies it covers. Onboarding another company later is a configuration.
03What does somebody need to know before they can work an item?: What is on the item. The movement or the row, the company that booked it, the checks that ran and what each one read, the ones that found nothing, and the specific thing that would settle it. That is the design goal: a case that can be worked without asking anybody.
04Who can see which companies?: Access is by company and by role. A person sees the companies they work and the actions their role allows, and every action they take is recorded against them. A center serving several countries usually needs that split before it needs anything else.
05What happens to an item nobody picks up?: It stays. It keeps its state, it keeps everything that was checked on it, and it never drops out of a count to make that count look better. If it is the kind of case that closes itself, the case says so, which is how the desk tells waiting apart from stuck.

Bring two companies and one week of work.

Two entities from the set you would start with, a week of statements and the ledger extracts behind them. We show you the queue those days produce, and what each case would arrive on your desk carrying.

Request a demo See the whole product

What it takes from you: statements and a ledger extract for two companies. Nothing is posted to your books.