DEV Community

Cover image for Modelling SDP as a Two-Stage Pipeline
Kristi Hampson
Kristi Hampson

Posted on

Modelling SDP as a Two-Stage Pipeline

If you think in pipelines, the Simplified Declaration Procedure clicks into place quickly.

Stage one is the simplified frontier declaration. It carries reduced data, enough to obtain release. Latency at the border drops because there is less to submit and validate up front.

Stage two is the supplementary declaration. It carries the full payload and drives the duty calculation. It runs asynchronously, usually due by the fourth working day of the next month.

The link between the two stages is the part that matters most. Every frontier entry must map to its supplementary record, and you keep evidence for each release. The two-stage SDP customs pipeline describes exactly how HMRC expects that mapping to hold.

Duty settles through a monthly deferment, so the finance leg is batched rather than per-transaction. That batching is where the cash-flow benefit comes from.

The failure mode is a broken link between stages. If a frontier entry has no matching supplementary record, or the totals do not reconcile against the deferment statement, you carry compliance risk. Carry frontier data forward automatically and the error rate drops.

Watch a demo

Top comments (0)