Specs
Export Week specs
Implementation notes and key reference numbers for Export Week.
How Export Week specs map to a working week
The Export Week specs page turns those cross-border payment issues into a tighter reference for implementation and review. It helps teams document edge cases, decision points, and local constraints before they become support tickets.
For Export Week specs, start with the transfer route, the destination country, and the exact handoff that can stall release. Cross-border files often depend on bank cut-off times, beneficiary name checks, SWIFT references, and South African proof of payment that matches the commercial invoice. Teams in Johannesburg, Durban, and Cape Town usually need one note that finance, ops, and customer support can read without swapping terms halfway through.
Capture the first reference set before anyone resends instructions or edits banking details. Record invoice number, bank reference, value date, and the proof screen used for internal checking. Later disputes are easier to review when those details sit beside the shipment or order record.
Cross-border fields worth pinning
Use these specs to define which identifiers are mandatory before money moves or stock leaves. Most teams need a short decision list covering settlement timing, proof format, release rules, and who signs off an exception. Fancy alternatives matter less than one repeatable method that survives month-end pressure.
Link Export Week specs to the matching Rails note, then record any operational exception in Playbooks or Signals before scope expands. Add a final payment verification step before collection, dispatch, or customer release, especially where foreign references and South African bank records can differ. Your contact form message should include a screenshot of the current payment, checkout, or release flow.
- Reference points for export payment release
- Value date checked against dispatch deadline
- Screenshots kept with the finance record
Checks shaped by SA banking
Export Week specs are useful when cross-border timing collides with local settlement habits and internal handovers. One team may be waiting on a SWIFT copy, another on Instant EFT proof, while support is trying to explain why shipment release still needs verification. The note should separate customer-facing wording from the back-office check that actually authorises movement.
South African trading conditions change how these specs are written. Load-shedding can interrupt proof capture, branch visits still happen when a payer wants help in person, and courier collection times can force an earlier internal cut-off than the bank requires. Document the local constraint next to the payment rule so reviewers can see why the process exists.
Operated by Astros Marketing (Pty) Ltd from 2 Makro Place, Sunnyrock 1401.
Export Week implementation prompts
Use Export Week when your team needs clear notes on cross-border timing, local settlement, and proof of payment.
Write the spec while the payment trail is still visible in the bank view and order system. Pair it with the relevant process note and any proof requirements used for sign-off, release, or audit checks. That keeps the reference useful when the same issue returns during another export cycle.
What our Real-Time Payments customers say
Verified Google reviews