Card-policy workbook and issuer-limit change log — "Cards stay above the new policy limit because the sheet was not pushed to the issuer"
Why the manual spreadsheet breaks financial controls and how a deterministic workflow replaces it.
Corporate card policy limits are edited in a workbook that is supposed to be sent to the issuer, so a lowered limit stays on the card until someone uploads the sheet.
Cards stay above the new policy limit because the sheet was not pushed to the issuer, and spend continues on a limit the policy already revoked.
Card-policy registry that versions each limit change and pushes it to the issuer before the next billing cycle can open.
Limit assertion: a card cycle cannot open if the issuer limit differs from the policy version in force on the cycle start date.
Three-stage comparison between manual workbook reconciliation and automated rule-based execution.
Card limits are edited in a workbook the issuer never receives.
Cards stay above the new policy limit because the sheet was not pushed to the issuer.
A cycle cannot open if the issuer limit differs from the policy version.
A card cycle cannot open if the issuer limit differs from the policy version in force on the cycle start date.
Adjacent spreadsheet failure modes in the same APQC Category 9 process group.
Monthly cardholder reconciliation file and ERP upload batch sheet
Corporate card monthly reconciliation & expense coding tracker
T&E tax-data extraction sheet and year-end provision backup
Scope the replacement architecture for manual maintenance of corporate card policy limits or combine multiple failure modes in the directory.
