“Double refunds issued to clients because support and accounting operate in silos”
Manual Data Flow Trap
1
Silo
Ticket Credit
Support issues a Stripe credit from the ticket without checking accounting.
2
Duplicate
AP Credit
Accounting issues the same credit from the invoice list a day later.
3
Cash Leak
Recovery Chase
The double payout is found in the bank rec and clawed back if possible.
Root Operational Bottleneck
Refunds are issued from support tickets and again from accounting's payment log, because neither system knows the other already credited the customer.
Control Hazard & Audit Exposure
The same invoice is refunded twice, cash is recovered only if someone notices, and there is no single state that says whether a credit is requested, approved, or paid.
Manifests in: Zendesk customer credit request list and manual Stripe credit log
Deterministic Replacement (After)Golden Door Standard
Target Software Architecture
Bidirectional ERP-Payment Refund State Machine with Idempotency
Deterministic Pipeline Execution
1
One Record
Single Request
Support or billing opens one refund record keyed by invoice and reason.
2
Gated
Approval State
Policy routes the request; the processor is called only from this record.
3
Once
Idempotent Payout
A second request for the same invoice and reason is blocked as a duplicate.
Deterministic Software Pattern
Idempotent refund state machine shared by support and the payment processor, so a credit request can produce only one payout per invoice and reason.
Continuous Assertion Rule
Idempotency assertion: a refund cannot pay if another refund already exists for the same invoice, amount, and reason code.
Support issues a Stripe credit from the ticket without checking accounting.
2AP Credit
Duplicate
Accounting issues the same credit from the invoice list a day later.
3Recovery Chase
Cash Leak
The double payout is found in the bank rec and clawed back if possible.
Root Operational Bottleneck
Refunds are issued from support tickets and again from accounting's payment log, because neither system knows the other already credited the customer.
Control Hazard & Audit Exposure
The same invoice is refunded twice, cash is recovered only if someone notices, and there is no single state that says whether a credit is requested, approved, or paid.
Deterministic Replacement (After)Golden Door Standard
Target Software Architecture
Bidirectional ERP-Payment Refund State Machine with Idempotency
Deterministic Pipeline Execution
1Single Request
One Record
Support or billing opens one refund record keyed by invoice and reason.
2Approval State
Gated
Policy routes the request; the processor is called only from this record.
3Idempotent Payout
Once
A second request for the same invoice and reason is blocked as a duplicate.
Software Pattern
Idempotent refund state machine shared by support and the payment processor, so a credit request can produce only one payout per invoice and reason.
Continuous Assertion Rule
Idempotency assertion: a refund cannot pay if another refund already exists for the same invoice, amount, and reason code.
Related problems
Same Revenue Accounting catalog · unique PCF · stay on directory
“Double refunds issued to clients because support and accounting operate in silos”
Manual Data Flow Trap
1
Silo
Ticket Credit
Support issues a Stripe credit from the ticket without checking accounting.
2
Duplicate
AP Credit
Accounting issues the same credit from the invoice list a day later.
3
Cash Leak
Recovery Chase
The double payout is found in the bank rec and clawed back if possible.
Root Operational Bottleneck
Refunds are issued from support tickets and again from accounting's payment log, because neither system knows the other already credited the customer.
Control Hazard & Audit Exposure
The same invoice is refunded twice, cash is recovered only if someone notices, and there is no single state that says whether a credit is requested, approved, or paid.
Manifests in: Zendesk customer credit request list and manual Stripe credit log
Deterministic Replacement (After)Golden Door Standard
Target Software Architecture
Bidirectional ERP-Payment Refund State Machine with Idempotency
Deterministic Pipeline Execution
1
One Record
Single Request
Support or billing opens one refund record keyed by invoice and reason.
2
Gated
Approval State
Policy routes the request; the processor is called only from this record.
3
Once
Idempotent Payout
A second request for the same invoice and reason is blocked as a duplicate.
Deterministic Software Pattern
Idempotent refund state machine shared by support and the payment processor, so a credit request can produce only one payout per invoice and reason.
Continuous Assertion Rule
Idempotency assertion: a refund cannot pay if another refund already exists for the same invoice, amount, and reason code.
