Why a CFMS Bill Gets Rejected or Returned — and How to Fix It

Few things slow down a government payment more than a bill bouncing back from the treasury. For a Drawing and Disbursing Officer (DDO), a returned or rejected CFMS bill means re-work; for the employee or vendor waiting on the money, it means more delay. The good news is that the reasons bills get sent back are surprisingly repetitive — and once you know them, most are easy to avoid.

This guide goes through the common causes of returns and rejections in the Andhra Pradesh CFMS system and explains how to fix or prevent each one.

Returned vs rejected: know which you're dealing with

Before fixing anything, identify what happened:

• Returned / Objected — the treasury found a correctable issue and sent the bill back with a note. The bill is still alive; fix the issue and resubmit.
• Rejected — the bill was refused outright and usually has to be raised again. Rejections tend to point to a more fundamental problem.

For a fuller explanation of these and every other status, see what each CFMS bill status means.

1. Wrong or invalid budget head

Every bill must be drawn against the correct Head of Account. If the head is wrong, does not match the nature of the expenditure, or is not the one under which funds were allotted, the bill will be objected to or rejected.

Fix: double-check the Head of Account against the sanction order and the budget allotment before submitting. Make sure the major, minor and detailed heads all correspond to the type of payment. The CFMS Object Heads list shows the correct Detailed and Sub-Detailed Head codes for each kind of expenditure.

2. Insufficient or lapsed budget allotment

CFMS checks whether enough budget is available under the relevant head before a bill can pass. If the allotment is exhausted, has not been released, or has lapsed at year-end, the bill cannot go through.

Fix: confirm that budget has been distributed and is available for the head before raising the bill. Near 31 March, be especially careful — allotments not used in time lapse, and bills against them will fail.

3. Missing or incorrect supporting documents

Many claims require enclosures — sanction orders, vouchers, certificates, or proof of expenditure. Medical reimbursement, travelling allowance, and contingent bills are common examples. If a required document is missing or does not match the claim, the bill is returned.

Fix: keep a checklist of the documents each bill type needs and attach them all before submission. Ensure amounts and dates on the documents match the figures in the bill.

4. Beneficiary or bank account problems

If the beneficiary's bank account details are wrong, inactive, or not properly mapped in the system, the payment cannot be released even after the bill is passed. Mismatched names or incorrect account numbers are frequent culprits.

Fix: verify the beneficiary's account number, IFSC and name against bank records before submitting. Correcting account details after a failure is slower than getting them right the first time.

5. Duplicate or double claims

If the same claim is submitted twice — for instance the same allowance billed in two separate bills — the system or the verifying officer will reject the duplicate.

Fix: maintain a clear bill register so the office can see what has already been claimed. Before raising a bill, confirm the same amount has not already been submitted.

6. Calculation or amount errors

Arithmetic mistakes, wrong rates, incorrect deductions, or a total that does not add up will cause an objection. Even small inconsistencies between the figures and the supporting documents can hold a bill up.

Fix: re-check all calculations, including deductions and recoveries, and make sure the net amount is consistent throughout the bill.

7. Rule or sanction issues

Some bills require a specific sanction or must comply with a particular government order. If the necessary sanction is absent, has expired, or the claim does not follow the applicable rule, the treasury will not pass it.

Fix: ensure the relevant sanction order is in place and valid, and that the claim is admissible under current rules before submitting.

8. Data entry and formatting mistakes

Simple keying errors — a wrong date, a transposed figure, an incorrect employee ID — are an avoidable but common reason for returns. The system is precise, and a small mismatch can stop a bill.

Fix: review every field carefully before submission. A two-minute check is faster than a full resubmission cycle.

A simple pre-submission checklist for DDOs

What to do once a bill is returned

1. Read the objection or remark carefully — it tells you what is wrong.
2. Fix exactly that issue; don't change unrelated parts of the bill.
3. Re-verify documents and figures around the corrected item.
4. Resubmit and track the status using the bill status checker.

For a rejected bill, you will usually need to prepare a fresh bill after addressing the root cause. If you are not sure why a bill failed, the office accounts section or treasury can clarify the reason recorded in CFMS.

The bottom line

Almost every CFMS rejection traces back to one of a few issues: the wrong head, missing budget, missing documents, bad bank details, or a duplicate claim. Building a habit of checking these before submission dramatically reduces returns — and keeps salaries, allowances and vendor payments moving on time.