Billing

Auto control sheet from WIR/MIR, auto deductions, compliance pre-verified, WO ↔ SES auto-match — bill cycle compressed.

What it is

Bill certification is where projects routinely lose time. Today: bill arrives; commercial team prepares control sheet manually; deductions calculated case-by-case; compliance check is a chase; WO ↔ SES match is manual; payment slips to D+45 or worse. The module auto-generates control sheets from closed WIRs, computes deductions, pre-verifies compliance (PF, ESIC, GST, TDS), auto-matches WO and SES in SAP — and releases payment on a compressed cycle.

Inputs

Triggers

·WIR closure in M19 auto-triggers bill workflow
·Vendor submits bill with measurement and rate
·CM and DCO review
·Compliance pre-check (PF, ESIC, GST, TDS)
·SAP SES (Service Entry Sheet) match
·MIS month-end cycle

Data reads

·WO terms from M14
·Amendment record from M15
·WIR/MIR closure from M19
·Material consumption from M17
·Labour deployment from M20
·Vendor compliance status from M13 and M20

Artefacts consumed

·Vendor bill submission with measurements
·Joint measurement sheets
·Test reports and certificates as applicable
·Compliance certificates

Tools & Techniques

Methods

·Control sheet auto-generation from WIR closures
·WO ↔ SES match automated against SAP
·Compliance pre-verification before bill enters the queue
·Deduction calculation from policy (retention, debit notes, ESIC, PF)
·Bill cycle-time tracking — D+12 from WIR target
·Payment release workflow with Finance and Treasury

Policies

·bill certification policy with cycle-time targets
·Deduction policy (retention %, debit note rules)
·Compliance pre-verification policy
·Payment release threshold policy

Decision rules

·Compliance lapse holds bill — no exceptions
·WO/SES mismatch holds bill until reconciled
·Deductions auto-calculated; manual override requires DCO approval
·Cycle-time target D+12 from WIR; breach surfaces in MIS

Outputs

Artefacts produced

·Control sheet per bill cycle
·Certified bill with deduction calculation
·Payment release record
·Bill cycle-time MIS
·Compliance verification log

Data writes

·Bill status updated through certification → payment lifecycle
·SAP payment record updated on release
·Vendor payment history updated in Vendor 360
·Budget commitment reconciled against actual

Downstream triggers

·Payment release closes the WO-WIR-Bill cycle
·Bill cycle data feeds Vendor 360 (M13) and budget actuals (M11)
·Cycle-time breach triggers MIS alert and CPT review
·Compliance hold pattern flags vendor in M13

Stakeholders

CommercialOwns bill workflow end to end
VendorRaises performa invoice against WO and closed WIRs
CMBill substantiation from WIRs
CPTWO and amendment context
Commercial HeadFinal bill approval
FinancePayment release

The flow

01Control sheet auto-generated from WIR/MIR closures
02Vendor performa invoice received
03Deductions calculated — advance recovery, quality issues, retention
04Compliance verification — PF, ESIC, GST, TDS
05WO ↔ SES auto-match in SAP
06Bill approval by Commercial Head
07Payment release by Finance

State change

Before

Bill cycle is D+30 to D+60; control sheet manual; compliance is a chase.

After

Bill cycle is D+12 from WIR; auto control sheet; compliance pre-verified.

Real-world example

BA20 L9 — WIR closed 02 May. Control sheet auto-generated 03 May. Vendor performa invoice (KCL, ₹2.8 Cr) received 04 May. Deductions: 6.5% retention + advance recovery. Compliance pre-verified. WO ↔ SES match passed. Bill approved by Commercial Head 09 May. Finance released 14 May — D+12 from WIR. Goel Power held on compliance flag: PF April not paid.

Artefacts

·Control sheet
·Performa invoice
·Deductions calculation
·Compliance verification records
·WO ↔ SES match log
·Bill approval record
·Payment release record

Pain today

Bill arrives; control sheet is a manual exercise; deductions case-by-case; compliance verification is a chase. WO ↔ SES match is manual. Payment slips to D+45 or worse, eroding vendor trust.

Integrations

BandhooSAP