Reconcile Inventory and Maintain Audit Readiness
Learning Objectives
After completing this unit, you’ll be able to:
- Describe how the Sample Inventory Management dashboard supports daily inventory stewardship.
- Distinguish the core inventory operations used to move and correct field stock.
- Explain when to use Initial, Ad Hoc, Periodic, and Audited inventory counts.
- Describe how discrepancy reconciliation keeps physical and digital inventory aligned.
Move from Visit Enforcement to Inventory Stewardship
In the previous unit, you saw Sample Management validate sample drops at the moment of distribution. That protects each transaction, but compliance doesn't end when the visit is submitted. A broader question stays open. Does the representative's physical inventory still match the system record?
Physical stock drifts for various reasons. A shipment arrives to acknowledge. A colleague needs a transfer. Damaged units go back to the warehouse. A prior entry needs a correction. A count turns up fewer units than expected.
In this unit, you use the Sample Inventory Management dashboard to manage that ongoing activity. You review inventory operations, perform counts, reconcile discrepancies, and build the audit evidence behind compliant sample distribution.
Use the Dashboard as the Inventory Hub
The Sample Inventory Management dashboard gives representatives one place to manage trunk stock, the sample inventory they physically carry and are accountable for in the field. It pulls daily inventory activity into a single workspace, organized into six components.
The dashboard's components run on Apex controllers that require the Life Sciences Core permission set. Without it, the dashboard renders empty or returns errors, so confirm representatives have the permission set before they rely on the hub.
The dashboard includes six core components.
-
Disbursements (1) shows sample products disbursed over a selected period, with time filters like 3, 6, or 12 months to gauge recent activity.
-
Inventory Count Assessments (2) is where reps complete and review Initial, Ad Hoc, Periodic, and Audited counts.
-
Manage Batch (3) lists the product batches assigned to the rep, so they can check expiration dates, batch numbers, and whether an allocation is active.
-
Received Inventory (4) shows inbound stock awaiting confirmation. Shipments come from warehouse fulfillment, and transfers come from other reps.
-
Inventory Storage Addresses (5) shows where the rep's inventory is stored, with access to the full address list for updates.
-
Inventory Timeline (6) shows inventory operations and product requests in chronological order, including transfers, returns, adjustments, and replenishment requests with product, quantity, date, and status.
For Cumulus, this dashboard gives Evan a single place to manage his full sample inventory across products and batches.
Manage Stock Between Visits
Sample work continues between provider visits, and a representative handles it from the Sample Inventory Management dashboard. Each action creates a record, updates the balance, and posts to the inventory timeline with a status. The rep starts an inventory operation or a product request from the timeline's add menu, and acknowledges inbound stock in the Received Inventory component.
A handful of actions carry the day-to-day work, each with a distinct job.
- Acknowledgment is the receipt action in Received Inventory that accepts an inbound shipment or transfer. The stock isn't available to use until the rep accepts it.
- Transfer Out is an inventory operation that sends stock to another rep. The sender's balance drops, and the recipient acknowledges the inbound transfer.
- Return is an inventory operation that logs damaged, obsolete, or unwanted stock returned to the warehouse and updates the digital balance.
- Adjustment is an inventory operation that corrects a documented inventory error and updates the digital balance.
- Product Request is a replenishment order, not an inventory operation. It records demand for new stock, and the balance rises only after the request is fulfilled and acknowledged.
For Cumulus, Evan manages several products through the dashboard. During one field cycle he focuses on Immunexis, because supply is tight and the product carries heightened scrutiny. He transfers 20 units to a nearby colleague, returns 15 damaged units to the warehouse, submits a replenishment request, and records an adjustment for a prior entry error.
Each action moves the inventory picture in a specific way. Transfers and returns reduce available stock, requests start a replenishment, and adjustments correct the digital balance. Together they show how physical stock moves between visits, and inventory accuracy depends on capturing every movement, not just the samples handed to providers.
Verify Physical Stock with Count Assessments
Inventory operations record movement. Count assessments verify that the physical stock still matches the system record. That verification is essential for sample compliance. A rep can have a complete transaction history and still find a mismatch during a physical count. A damaged unit was set aside, a transfer was delayed, or a prior entry used the wrong quantity.
The Inventory Count Assessments component supports four count types to verify quantities.
- Initial establishes the verified starting inventory. It comes first, before regular inventory activity begins.
- Ad Hoc is an on-demand count outside the regular schedule. A rep runs one before a heavy visit day or after noticing a possible mismatch.
- Periodic is a scheduled count required by company policy, and it proves inventory is verified at defined intervals.
- Audited requires manager or peer review before it's finalized, for cases that call for a higher level of verification.
One setup step affects this component. The Purpose field on Inventory Count Assessment is a picklist that ships without values, so an admin adds the values the team uses, such as Reconciliation, before reps can submit counts.
For Cumulus, Evan completes an Initial count to establish his baseline before field operations begin. Later, during the Immunexis launch, he starts an Ad Hoc count after several transfers and returns shift his stock position. During a count, he selects the product, reviews the system count, enters the actual physical count, and submits the assessment. If the values match, the record is confirmed accurate. If they differ, the system moves into the discrepancy workflow.
Count assessments give the organization evidence that balances are checked against physical stock. They turn sample accountability into a recurring field process.
Reconcile Inventory Discrepancies
A discrepancy appears when the physical count and the system count don't match. Representatives don't edit the inventory balance directly. Sample Management handles the correction through the count assessment workflow, so the count, reason, adjustment, and final balance stay connected.
During the assessment, the dashboard shows the Total System Count. The rep enters the Actual Stock Count from the physical count. When the two values differ, the system requires a discrepancy reason before the assessment can be submitted.
For Cumulus, Evan starts an Ad Hoc count for Immunexis after a busy week of field activity. The system count shows 100 units, but he counts 95. He selects a discrepancy reason and submits the assessment.
Sample Management calculates the 5-unit difference and creates a corrective adjustment. Evan's Product Item updates to 95 units. The adjustment appears in the timeline with its product, quantity, date, and status.
This workflow preserves the audit trail. The system records what the rep counted, what it expected, why the values differed, and how the balance was corrected. That documentation helps compliance teams explain inventory movement without reconstructing events from separate notes.
Connect the Audit Trail Across the Lifecycle
Sample compliance depends on a complete, connected record of custody, movement, distribution, and reconciliation. Each part of the workflow you built produces a different kind of evidence. The inventory hierarchy shows where stock lives and which batch supplied it. Visit disbursements show which accounts received samples. Inventory operations explain movement between visits. Count assessments and their adjustments verify and correct the physical balance.
Because those records connect, compliance teams can trace a single sample product from end to end. They follow it from batch allocation, to representative inventory, to field disbursement, transfer, return, count, or adjustment.
For Cumulus, the Immunexis audit trail doesn't depend on Evan's memory or a side spreadsheet. The system captures the operational facts as the work happens. When a discrepancy appears, the count, reason, adjustment, and updated balance stay connected.
Wrap Up
For Cumulus, the Immunexis launch now runs on a system of record instead of memory and spreadsheets. Evan carries stock he can account for, every drop is checked before it's recorded, and the audit trail stays current as he works.
Across this badge, you built the framework behind that outcome.
- You separated the commercial product foundation from the sample management layer, then configured the inventory hierarchy that tracks stock and preserves batch-level accountability.
- You set the compliance guardrails. Provider Sample Limits cap how much an HCP or healthcare organization (HCO) can receive, and Territory Product Quantity Allocations cap how much a territory can distribute in a period.
- You followed sample drops through visit submission, where valid drops update the record chain and blocked drops stop before they can be recorded.
- Finally, you used the Sample Inventory Management dashboard to manage stock between visits, run count assessments, and reconcile discrepancies.
The result is control that holds up to scrutiny. Admins define the structure and rules, representatives work within them, and the system records each movement, validates each drop, and keeps the audit trail current as work happens.
To go deeper on the configuration details behind each step, check out the Resources!