BAST Checklist and BPK Audit Documentation for IT Equipment Rental

Messy documentation rarely causes problems when equipment first arrives — it surfaces a year later, when a BPK or Inspektorat auditor asks for proof of a specific unit's handover and nobody can produce it immediately. For rental-based procurement, this paper trail matters more than for a purchase, since there's no fixed-asset record automatically preserving history.

This is a practical checklist: which documents you need, when to create them, and the common mistakes that leave a committee scrambling at audit time. For procurement track and terminology context, see the government/SOE laptop rental procurement guide first.

Start of Contract

• KAK and HPS, kept as part of the contract package.
• Signed SPK/contract with technical specs and unit count attached.
• Initial handover BAST — unit count, serial/barcode per unit, condition, date.
• Photo documentation of received condition, for later warranty/damage claims.

During the Contract

Document every unit replacement (old and new serial numbers, date, reason) and keep SLA compliance records if the contract specifies response times.

End of Contract

A return BAST whose unit count reconciles against the initial BAST plus documented replacements, and — critically, and most often missing — a data-erasure certificate for any device that held institutional data during the rental.

Common Auditor Findings

The three most common gaps: initial and final BAST unit counts that don't reconcile without written explanation, missing replacement records despite serial numbers visibly differing between received and returned units, and no proof of data erasure for units that held institutional data. All three are entirely preventable with consistent documentation from day one.

Want a vendor whose documentation is already in order from day one? Government laptop rental or SOE laptop rental from Automata Info Nusantara.