Skip to main content

Invoice Assignment Rules

Invoice Assignment Rules automatically assign incoming invoices to your team, so nobody has to hand them out and nothing sits unowned. You choose how invoices are shared across the team, which days each person works, and optionally which error codes go to which specialist.

Who can use it: Organisation admins. Open Invoices and click the Assignment Rules cog icon in the toolbar.


How it works

  1. Turn on Assignment rules. From then on, every new invoice that arrives is assigned the moment it's created.

  2. Choose a Distribution method -> Round Robin or Balanced (explained below).

  3. Set up your Team Members -> who's in the rotation, which days they work, and whether they handle specific error codes.

  4. Save Configuration. Your rules apply to all future invoices. Anything already assigned stays where it is.


Apply to Unassigned

If invoices arrived before you turned the rules on (or while everyone was away), click Apply to Unassigned to distribute everything currently unassigned using your saved rules. The count in the footer shows how many are waiting. It processes up to 500 at a time; click again if more remain.


Team Members

Each person on the roster has:

  • On / off switch -> switch someone off while they're on leave and they'll stop receiving invoices. Their settings are kept for when they're back.

  • Days -> the days they receive invoices. Someone rostered Mon–Wed won't be given anything on a Thursday, even if they're switched on.

  • Handles: All invoices / Specific error codes -> see Routing by error code below.


A person needs to be switched on and rostered for today to receive an invoice. If nobody qualifies, the invoice stays unassigned until someone is available or you click Apply to Unassigned.


Distribution: Round Robin

Round Robin hands invoices out in turn, one each, around the team.

How it decides: the team is in a fixed order, a pointer remembers who received the last invoice, and the next invoice goes to the next available person after them. When it reaches the end it starts again from the top. People who are switched off or not rostered today are skipped.

Example -> three people, all rostered today

Amelia, Ben and Priya are all set to All invoices, so this is the rotation on its own, no error-code routing involved.

Invoice

Goes to

1

Amelia

2

Ben

3

Priya

4

Amelia

5

Ben

If Ben is off on Wednesday, Wednesday's invoices alternate Amelia → Priya → Amelia → Priya, and he rejoins the rotation on Thursday.

Good for: teams where everyone should get an equal number of invoices, and you don't need the system to account for how busy someone already is.

Note: Round Robin doesn't look at existing workload. If one person also handles specialist codes (see below), they'll receive their share of the rotation plus their specialist invoices.


Distribution: Balanced

Balanced gives each new invoice to whoever has received the fewest invoices today.

How it decides: Caresquare keeps a count of how many invoices each person has been auto-assigned today (Sydney time). The next invoice goes to the available person with the lowest count. When two people are tied, whoever received an invoice most recently is skipped, so it alternates fairly.

The count goes down when a person archives an invoice, so completed work frees up capacity. Counts reset at midnight.

Example -> three people; Amelia already has 4 today, Ben 2, Priya 2

Same three people, all on All invoices. Starting from zero, Balanced behaves like Round Robin, 1 → Amelia, 2 → Ben, 3 → Priya, because everyone is tied. The difference appears once counts diverge, so pick it up mid-morning:

Invoice

Counts before

Goes to

1

Amelia 4 · Ben 2 · Priya 2

Ben (tied lowest)

2

Amelia 4 · Ben 3 · Priya 2

Priya

3

Amelia 4 · Ben 3 · Priya 3

Ben (tied with Priya; Priya was last)

4

Amelia 4 · Ben 4 · Priya 3

Priya

Amelia doesn't receive anything until the others catch up to her.

Good for: teams where some people also handle specialist work or work part-days. Balanced self-corrects; Round Robin doesn't.


Routing by error code

Every invoice Caresquare processes is checked for problems, a bank account that doesn't match the provider's, a participant that couldn't be found, totals that don't add up, and so on. Each problem is an error code; you'll recognise them from the Warnings column on the Invoices page.

You can tell Caresquare that a particular person handles certain error codes. Invoices carrying any of those codes go to them ahead of the normal rotation.

Setting it up

On a team member's card, switch Handles from All invoices to Specific error codes, then choose the codes. Two options follow:

  • Leave "also takes a share of all other invoices" unticked -> the person is a specialist. They receive only invoices with their codes and are taken out of the general rotation.

  • Tick it -> the person is your go-to for those codes but also takes their normal turn on everything else. This suits small teams where nobody can be a full-time specialist.

The status line under their name tells you which you've got: Only invoices with their error codes or Their error codes first, plus a share of everything else.

How invoices are routed

For each new invoice:

  1. Does anyone available handle one of its error codes? If yes, it goes to one of those people (using your Distribution method to choose between them if there's more than one).

  2. Otherwise, it goes to the general rotation -> everyone on All invoices, plus anyone with the "also takes a share" box ticked.

Codes nobody handles are simply ignored for routing. An invoice with a handled code and an unhandled one is still routed to the handler.

A specialist gets every invoice with their codes. If only one person handles a code, they receive all invoices carrying it, whichever Distribution method you use, the method only decides between people when more ,than one handles the same code. Before giving a common code (such as Check dates or Missing participant) to a single person, check how many invoices a day carry it. If it's a lot, give the code to two or more people so it's shared.

Example

Four people, Round Robin:

Member

Handles

Amelia

All invoices

Ben

Specific: Check dates — also takes a share

Priya

All invoices

Daniel

Specific: Check bank account details — specialist only

General rotation: Amelia → Ben → Priya (Daniel is specialist-only).

Invoice

Warnings

Goes to

Why

A

Check bank account details

Daniel

he handles it

B

Missing participant

Amelia

nobody handles that code → rotation

C

Check dates

Ben

he handles it

D

Ben

his turn in the rotation

E

Check bank account details, Check dates

Daniel

two handlers; they take turns

F

Check dates

Ben

G

Missing participant

Priya

rotation

H

Check bank account details

Daniel

Daniel never appears in B, D or G because he's specialist-only. Ben appears both for his code (C, F) and for his rotation turn (D) because his share box is ticked.

Example

Four people, Balanced:

Member

Handles

Amelia

All invoices

Ben

Specific: Check dates — also takes a share

Priya

All invoices

Daniel

Specific: Check bank account details — specialist only

General rotation: Amelia, Ben, Priya (Daniel is specialist-only).

Invoice

Warnings

Counts before (A · B · P · D)

Goes to

Why

A

Check bank account details

0 · 0 · 0 · 0

Daniel

only handler

B

Missing participant

0 · 0 · 0 · 1

Amelia

nobody handles it → rotation; all tied, first by name

C

Check dates

1 · 0 · 0 · 1

Ben

only handler

D

1 · 1 · 0 · 1

Priya

fewest in the rotation

E

Check bank account details, Check dates

1 · 1 · 1 · 1

Daniel

two handlers tied; Ben was picked more recently

F

Check dates

1 · 1 · 1 · 2

Ben

only handler

G

Missing participant

1 · 2 · 1 · 2

Amelia

Amelia and Priya tied; Priya was picked more recently

H

Check bank account details

2 · 2 · 1 · 2

Daniel

only handler

End of the run: Amelia 2 · Ben 2 · Priya 1 · Daniel 3 (Round Robin gave Amelia 1 · Ben 3 · Priya 1 · Daniel 3).

The difference is invoices D and G. Under Round Robin, Ben got D because it was simply his turn; under Balanced he's skipped because his Check-dates invoice already put him ahead, so D goes to Priya and G to Amelia. That's Balanced doing what it's for: someone who also handles specialist work doesn't end up with more than their colleagues.

Daniel's total is the same in both modes, he's the only person handling Check bank account details, so every one of those invoices is his regardless of method.

What happens when a specialist is away

If nobody who handles a code is switched on and rostered today, those invoices go to the general rotation like any other. Nothing is held back. When the specialist returns, new invoices with their codes route to them again; anything assigned in the meantime stays with whoever received it.

Which error codes can be routed?

All the codes Caresquare detects when an invoice first arrives -> bank details, totals, item codes, missing or multiple participants/providers, GST, dates, duplicates, flagged providers and participants, first-time providers, compliance orders, overlapping lines and balance checks. A few codes that are only determined later in processing (provider limits, SIL/STA documentation, custom QA rule violations, funding period and early-childhood checks) aren't available for routing yet.


Frequently asked questions

Will turning this on move invoices people already have? No. Assignment only ever happens to invoices with no assignee. Nothing is reassigned automatically, by rules or by Apply to Unassigned.

Two people handle the same error code, who gets it? Both are candidates, and your Distribution method decides: Round Robin alternates between them, Balanced picks whoever has fewer today. There's no priority between people; if you want one person to get a code, give it to one person.

Someone with "Specific error codes" is getting more than everyone else. If they also take a share of the rotation, they receive their specialist invoices plus their turn, Round Robin can't see the extra. Switch to Balanced and it will even out automatically, or untick the share box to make them specialist-only.

One person is getting almost everything. They probably handle a code that appears on most of your invoices. Routing gives every invoice with that code to its handler, so the volume follows the code, not the method. Add a second handler for that code so the two of them share it, or take the code off them so those invoices go back into the rotation.

Why did an invoice go to the general rotation when it had a code someone handles? That person was switched off or not rostered for the day. Check their card.

Nothing is being assigned. Check that Assignment rules is on and that at least one person is switched on and rostered today. If every team member is set to Specific error codes without the share box, invoices with no matching code have nowhere to go; the modal warns you about this.

Does Balanced count invoices I assign by hand? No, only automatic assignments count toward the daily total, and only archiving reduces it.

What time zone do "today" and "days" use? Australia/Sydney.

Did this answer your question?