Principal Tax Data Assurance Specialist — Withholding Ledger and GST Reconciliation

The mandate

Tax analysts in a technology-finance operation repeatedly repair supplier and ledger extracts before they can support Indian withholding and GST compliance. Those repairs are poorly linked to payment events, master-data changes or journal approval, making subsequent reproduction difficult. The Principal Tax Data Assurance Specialist defines and independently tests reconciliation and exception controls for selected populations, while approved contract classifications and tax positions remain unchanged. A four-month engagement beginning on 26 October 2026 will deliver a lineage bridge, controlled reconciliation workbook and an internally operated compliance-evidence process.

The first milestone on 26 November 2026 is a population diagnostic reconciling supplier, payment and ledger records with quantified breaks and source ownership. The second on 8 January 2027 is the designed reconciliation and correction-control model demonstrated on two historical periods. The final milestone on 26 February 2027 is two live-cycle replays, resolved test findings and the operating guide. Corrections must retain their original source and approval; a balanced output that silently overwrites an identifier or tax amount cannot satisfy the method's purpose, even if the total agrees to a filed return.

Acceptance sits with the national tax head and finance-data control manager. The diagnostic must tie populations to agreed control totals and document exclusions. Design acceptance requires traceability of duplicate suppliers, reversals, part-payments and late journals through the worked test set. Final acceptance requires internal analysts to reproduce the bridge, identify exceptions and demonstrate authorised corrections without consultant intervention. The fee is earned 25% on the diagnostic, 35% on the tested control design and 40% on live transfer, independent of any change in tax paid or future authority assessment.

The sponsor supplies approved technical positions, master-data history, payment records, ledger extracts and eleven contributors, including access to source-system owners. Four days weekly are reserved for Bengaluru-led analysis and Hyderabad workshops. Contract tax interpretation, return filing, application procurement and production-system configuration are excluded. Additional entities, historical periods or compliance outputs require a priced change agreement. The deliverable must leave a practical exception route and trained owners rather than an elaborate data map maintained outside daily operations. Sensitive supplier information will stay within agreed access and retention controls throughout delivery.

What you will own

• Reconcile the selected supplier, payment and ledger populations to approved control totals, identifying missing or duplicated events before downstream tax outputs are treated as reliable simply because their totals appear plausible.
• Construct the lineage bridge with stable identifiers and correction history, showing how each material compliance amount derives from original events and where authorised judgement or data repair enters the pathway.
• Design exception controls for reversals, partial payments and late journals, assigning accountable source owners rather than allowing tax analysts to resolve every discrepancy through an undocumented adjustment in the final workbook.
• Validate correction approval and replay on two historical periods, proving that the method preserves original evidence while reproducing the accepted population under changed supplier identifiers or transaction timing.
• Run live-cycle replays through internal analysts and source owners, recording unresolved breaks and failed controls so acceptance demonstrates practical operation instead of a consultant-repaired final compliance schedule.
• Transfer the controlled workbook and operating guide with version ownership, source-change triggers and escalation examples, ensuring future master-data or ledger changes do not silently invalidate the reconciliation design.

Candidate qualifications

• Demonstrate practical tax-data assurance in Indian withholding, GST or comparable transaction-based compliance, with the ability to reconcile supplier, payment and ledger events. Describe a population you rebuilt where a plausible total concealed missing or duplicated transactions. Explain your source method and correction controls, distinguishing evidence improvement from a technical tax reclassification that belongs to the appointed tax owner.
• Bring twenty-two to twenty-eight years in tax, finance controls or senior compliance practice, including substantial Indian operating experience and a rigorous professional foundation. You must understand why identifiers, reversals and timing affect compliance populations, and recognise when a reconciliation issue needs accounting or tax interpretation rather than a mechanical balancing entry that merely makes the workbook agree.
• Evidence consulting delivery with traceable artifacts, historical tests and internally reproduced live cycles. Show how you handled a source-data weakness without silently changing the original record, how acceptors reviewed residual breaks and how internal owners demonstrated independence. Controlled analytical reasoning, transparent model maintenance and practical transfer to tax analysts are essential to sustaining the accepted reconciliation method when source data changes.
• Reserve four days each week across the four-month programme and facilitate difficult ownership decisions across tax, supplier operations and finance. You should have coached analysts in replay and exception reasoning, protected sensitive supplier data and agreed scope changes before expanding the population. Clear judgement about where the data design ends and technical tax or production-system authority begins is essential to a usable, bounded result.

Application

Applications for this mandate are received in one way only: through the India Board Terminal's application process. It is automated end to end. Your Executive Passport travels to the mandate holder in its confidential form, your answers to the three questions below are read before anything else in your file, and every stage that follows is recorded on your applications page.

There is no address to write to and no intermediary to call. The mandate holder reads what the Terminal delivers and nothing else, which is what keeps the process the same for every applicant and keeps your name out of it until you release it. Applications close on 10 October 2026. Mandate reference CVU-CON-2026-IND-035.