Public Statum product - Case study
Car import duty calculator: making the assumptions visible
A vehicle name alone is not enough to produce a useful duty estimate. We built a calculator that connects the selected vehicle, its CRSP record, and the separate tax components in one result.
By Statum Company Ltd - Published
Try the import duty calculator ->The difficult part is choosing the right inputs
Two vehicles with similar names can have different engine capacities, fuel types, or CRSP records. A calculator that picks the first name match can give an apparently precise answer based on the wrong vehicle.
Our public tool asks for make, model, registration and import dates, engine capacity, fuel type, and vehicle category. It also accepts an optional tariff code. These inputs feed a calculation that keeps vehicle matching separate from valuation and tax arithmetic.
What we built
- Searchable vehicle selectors built from the available KRA CRSP records.
- An explicit confirmation step when more than one CRSP record matches the selected details.
- Separate values for customs value, import duty, excise duty, VAT, IDF, RDL, and the estimated total.
- A manual CRSP option with warnings when an official record has not been matched.
A match must be explainable
The implementation looks for records matching the vehicle details. If several records remain, it requires a record selection before proceeding. It also checks that a selected record still belongs to the current inputs. Changing the vehicle details cannot silently reuse an unrelated record.
When someone supplies a manual CRSP value, the result identifies it as manual. That distinction matters because an entered value and a matched source record are different kinds of evidence. The result carries the CRSP source and any warnings alongside the figures.
Keeping valuation and arithmetic separate
The code separates vehicle age, CRSP lookup, customs valuation, and excise-rate selection. It uses decimal arithmetic for the tax components and an explicit rounding step for displayed money. This makes it possible to inspect a component without treating the whole calculation as one formula.
The service also rejects impossible date sequences, such as registration after the expected import date. Missing engine capacity is handled according to fuel type. These checks are part of the calculation flow, so they apply before a result is returned.
The live page shows its valuation basis and links to the source schedules. It labels the output as an estimate and explains that KRA makes the final assessment. We have not presented the tool as a KRA approval or a substitute for customs documentation.
Sources a reader can inspect
KRA explains the role of the CRSP list and vehicle depreciation in its CRSP clarification. The live calculator links to the valuation workbook and other references used for its displayed assumptions.
The case study records the software's behaviour rather than quoting tax rates that may change. Before relying on an estimate, the user still needs the right vehicle documents, source schedule, and applicable customs treatment.
Where this fits in a larger system
For an importer or dealership, the estimate may be one step between a vehicle record, a customer quotation, and an approval. Keeping the selected record and assumptions with that quotation gives the next person something concrete to review.
Our business systems and workflow automation service covers those connected records and approvals. The salary calculator case study describes another public Statum product where the breakdown matters as much as the total.