Most police fine systems on FiveM boil down to a command, a number, and money disappearing from a player’s wallet. There’s no physical trace, no roleplay weight behind the interaction, and officers have no record to reference later. This citation script changes that by converting every fine issued into an actual inventory item — a printed citation sheet that the suspect carries on their person and can physically hand over, pay, or contest.

How the Citation System Works

When an officer issues a citation, the script generates a tangible item that lands in the suspect’s inventory. That item displays the suspect’s name, the specific charges, and the fine amount — readable by any player who inspects it. Officers can pull up unpaid citation records through MDT integration, and fines paid through the citation flow directly into the department’s society account rather than vanishing into the void.

• Citations created as physical inventory items — visible, inspectable, and transferable
• Citation sheet logs suspect name, offense description, and fine total
• Automatic penal code population with pre-configured amounts
• MDT integration (ps-mdt compatible) for checking outstanding citations per player
• Fine payments routed to the police department society/treasury account
• Compatible with qb-inventory and ox_inventory out of the box
• Qbox supported alongside QBCore

Why Inventory-Based Citations Matter for Roleplay

The difference between a database entry and a physical item in RP is significant. A suspect who has a citation in their inventory has to decide what to do with it — pay it on the spot, carry it to a courthouse interaction, or try to discard it. That decision creates roleplay that a backend fine entry never could. Officers also benefit: instead of hoping someone remembers they were fined, there’s a paper trail that exists inside the game world.

Framework Compatibility

Requires QBCore or Qbox. Inventory compatibility covers qb-inventory and ox_inventory natively; other inventory systems can be connected through the developer’s Discord support channel. This is a one-time purchase with no subscription — you own the resource.