These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Tax Collection System
- Features
- Collections
Collections
Import verified payment challans and apply each one to the taxpayer's posted demands.
OverviewPayment Challans×
Tax Collection System · Collections
New
Payment Challans
Cash receipts
| Provider event ID | Partner | Amount USD | Received at | |
|---|---|---|---|---|
| PEI-240 | BP-6607 | 70 | 07 Oct | |
| PEI-530 | BP-9501 | 480 | 07 Oct | |
| PEI-693 | BP-3469 | 50 | 07 Oct | |
| PEI-888 | BP-4668 | 350 | 08 Oct | |
| PEI-472 | BP-2647 | 700 | 12 Oct |
6 of 6 records
PEI-240Cash receipts · CR-92833
PartnerBP-6607
Amount USD70
Received at07 Oct
What you can do
Match every challan to what the taxpayer owes
Taxpayers pay through a bank or payment gateway using a challan. Each payment arrives as a cash receipt with the provider’s event ID, the taxpayer, the amount, the date and whether it is verified. A provider event already imported is refused, so the same challan is never counted twice.
The Collections Officer applies each verified receipt to the taxpayer’s posted demands. An application records the receipt, the document, the amount applied and the date. A receipt can only be applied to the same taxpayer’s documents, and never beyond the receipt amount or the amount still due. A wrong application is reversed by recording its reversal date, never deleted.
How the work is organized
- Verified receipts only. Only receipts the provider has confirmed are applied.
- Same taxpayer, within limits. Applications stay within the receipt and the demand’s remaining amount.
- Reversals on record. Every reversal keeps the original application visible.
What to agree during setup
Agree which banks and gateways issue challans and how their confirmations arrive. Decide how a receipt is applied when it does not name a demand, such as oldest first. Agree who may reverse an application and why. Plan how unapplied money is followed up.
Check the handoff on an actual case
The restaurant pays $1,650 at its bank with a challan referencing the license demand. The bank’s confirmation arrives as a verified receipt. The Collections Officer applies it to the posted demand, which leaves nothing outstanding.
The same week a bakery pays $2,500 against a $2,040 demand. The officer applies $2,040 and the remaining $460 stays unapplied on the receipt for follow-up. When the bank resends the restaurant’s confirmation the next morning, the duplicate provider event is refused.
At the end of each day, compare the total of verified receipts with the bank’s statement of challans, and the total applied with the posted demands that changed. Unapplied balances stay visible until the officer resolves them.
What your team sees
- Payment Challans — Verified receipts with provider event, taxpayer, amount and date.
- Cash Applications — Applications of receipts to demands, with amount, date and any reversal.
- Posted Demands — Posted documents ready for collection, with gross amount and posting dates.
Follow the work through
- Demand to collection: From posted demand to applied payment.
- Period close and receipt reconciliation: Reconcile collections at period end.
Plan the bank and gateway connections before importing challans.
What it keeps track of
Data model- Cash receipts
- Verified cash receipts imported from the collection provider.
- Cash applications
- Applications of verified cash receipts against posted documents.
- Accounting documents
- Assessed accounting documents carrying lifecycle, counterparty and gross amount.
- Business partners
- Taxpayers and counterparties assessed and collected against.
Who uses it
Permissions- Collections Officer
- , Revenue Accountant.
- The Collections Officer imports and applies receipts.
- The Revenue Accountant reconciles collections with the ledger.
Set up Tax Collection System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.