One travel number, seen twice
The travel row is 214,380.00 and two lenses watch it. The supplier lens shows who was paid: two central programs. The expense lens shows who traveled and why: 38 reports, 99 coded lines. Same dollars, nothing doubled.
◆ Coded travel, Maytwo categories, 99 lines.
| Category | Coded lines | May amount |
|---|---|---|
| Airfare | 52 | 121,400.00 |
| Lodging | 47 | 92,980.00 |
| Coded travel, May | 99 | 214,380.00 |
The category amounts are the two program bills on the supplier module’s spend page, line for line: airfare is the air program, lodging the hotel program. The total is the trial balance’s travel row, and neither lens adds a cent the other lacks. Sample values are illustrative, never client data.
◆ The reports behind the lines38 filed, most approved.
| Reports filed, May | Count |
|---|---|
| Approved | 33 |
| Awaiting approval | 4 |
| Sent back for fixes | 1 |
| Expense reports | 38 |
The 38 are the expense pipe on the journal source partition. Their journals put cost centers and projects on dollars the program bills already booked, adding nothing at the account level, and the audit sweep works the same population.
◆ The owned answertravel by worktag, finally.
Report lines land on the module star with traveler, category, and worktags, joined to the bills they substantiate. Travel by cost center, by project, or by traveler becomes a grouping, and it foots to the ledger because it never left it.
- central program
- The airline or hotel account billed to the company directly.
- coded line
- One report line carrying its category and worktags.
- substantiate
- Match the traveler’s lines to the program’s bill.
- worktag
- Workday’s tag set: cost center, project, region.