Invoice follow-up

1. Read the bank balance and the receivables due.
2. List known payments, including payroll and tax dates.
3. Project cash week by week for 13 weeks.
4. Mark the weeks where cash runs low.

Needs from you: Bank balance; Receivables and payables with dates; Payroll dates.

What it needs connected: Bank statement export; Accounting export file.

Where a person is designed to decide: It is designed only to read and report, so it has no approval step.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: GST.

1. Read the bank or card lines for the period.
2. Clean up vendor names and remove duplicate lines.
3. Assign each line to a category you defined.
4. A person reviews the odd ones and accepts the result.

Needs from you: Bank or card statement lines; Your list of expense categories.

What it needs connected: Bank statement export.

Where a person is designed to decide: A person reviews the odd ones and accepts the result.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: GST, UPI.

1. Read the submitted claims and receipts.
2. Compare each claim with the expense policy.
3. Flag claims that break the policy.
4. A person approves or returns each claim.

Needs from you: Expense claims; Expense policy.

What it needs connected: Expense claim file.

Where a person is designed to decide: A person approves or returns each claim.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.