Skip to main content

Manual Records Creation Page (Released May 20, 2026)

Giv introduces a dedicated workspace for admins to create and manage manually created billing records.

🧩 Overview

We're introducing the Manual Records Page — a dedicated workspace that makes it faster and easier for agency administrators to create and manage manually created billing records in Giv. Whether you're entering a handful of records or managing high volumes across multiple clients and programs, this new page gives you the flexibility, accuracy tools, and organization you need to get billing done with confidence.

Previously, the only way to manually create billing records was through the “Create New” button on the Service Records and Claims pages, and the Post Shift Report section of the Admin Dashboard — a workflow that was buried and limited in scope. The Manual Records Page changes that entirely, bringing manual billing to the forefront.


👥 Impacted Users

  • Agency Owners & Administrators — primary users of this feature for billing entry and management

  • Managers with partial admin permissions — may access depending on permission configuration

  • Billing-only users — this feature is specifically designed to support users who use Giv solely for billing (no care management workflows required)


New Features and Feature Enhancements

Customizable Views (Tabs) The Manual Records Page is organized around "views" — persistent, browser-like tabs that you create and configure to match your workflow. Each view keeps its filters and settings saved between sessions.

  • Create a new view by clicking the "+" button and naming it

  • Filter by a single client, code, or Staff member — the selected value will be pre-filled in the table

  • Filter by multiple clients, codes, or staff — selections appear as drop downs in each column

  • Choose no filter at all — all clients and codes will be available as drop downs; locations can be typed in freely

  • Archive views when they're no longer active

  • All records created within a view remain visible in your Service Records and Claims views even after archiving

Record Table & Columns Each view displays a structured table with the following columns, in this order: Client Name, Start Date/Time, End Date/Time, Service Code, Units, Staff, Location, Action/Status.

Field Locking Each column header includes a small lock icon (when creating records). By default, fields are unlocked. When you lock a field, the value from the previous row is automatically carried over when you add a new record — saving time during high-volume entry.

Auto-Calculated Units When you select a billing start date, end date, and service code, the number of units is calculated automatically based on how that code is configured. You can still override the calculated value manually. If the units entered don't match the time range for the selected code, you'll be prompted to confirm before continuing.

Budget Validation After units are entered, Giv checks whether the client has remaining budget for the selected code on the date entered. If a record would put a client over budget, you'll see a warning icon with a hover message — but the record can still be created if the user would like. This is advisory, not a blocker.

Date Range Search Each view supports date range filtering so you can quickly find records created within a specific period.


Feature Set and Affected Feature Areas

The Manual Records Page is a new standalone feature area within the Giv Web Dashboard. It also touches the following existing areas:

  • Service Records — records created via the Manual Records Page are visible here for record-keeping

  • Claims — claims generated from manual records are surfaced in the Claims view

  • Budgets — budget validation is triggered at record entry time

  • Billing Codes — codes drive unit auto-calculation and validation logic


🐛 Issues and Bug Fixes

This is a net-new feature release. No bug fixes are included in this release. Validation, error handling, and all edge cases have been reviewed and tested as part of the V1 scope.

Did this answer your question?