Payables and vendors
A vendor belongs to the books and says who it is — PAN, GST registration, MSME, TDS section — and a vendor's bill is matched against what arrived and what was agreed before it is owed.
The vendor was born in the kitchen store: a row on an outlet with a name, a GSTIN and the days it gives to pay. Right for "who delivered the tomatoes", wrong for "who do we owe" — a hotel with no restaurant could have no vendor, and the linen supplier serving three hotels was three vendors.
A vendor belongs to the account
One vendor across the group, with what the books need before a rupee is paid: PAN, GST registration type, MSME status (paid first, by law), the TDS section that applies, whether reverse charge applies, whether input credit is blocked. Duplicates are found by PAN and GSTIN.
The bank account is changed by two people
A vendor's bank account is proposed by one login and decided by a different one. That is the single control that stops the oldest fraud in accounts payable, and it is a trigger on the row, not a policy in a document.
A bill is matched before it is owed
What is owed is what the vendor's bill says — after it is checked against what arrived (the goods received note) and what was agreed (the order), within the tolerances the hotel sets, with the reasons for any difference in words. Approval records the TDS and writes one purchase journal. A cancelled bill reverses it.
Where the tax goes
The vendor's state and registration decide the tax; reverse charge is self-assessed; blocked credit is expensed. Each is a column the return reads.