Start with the submission schedule.

A calendar month is convenient when your reviewer requests one monthly report. A pay period is useful when expenses are submitted alongside a payroll cycle. A trip or client job may need a separate selection even if all its purchases fall in one month.

Ask which dates the report should cover and whether there is a separate submission deadline. Those are different questions. A period can end on a Friday while the reviewer expects the completed report later; do not infer a deadline from the date range alone.

A two-week period can cross a month boundary.

For an illustrative reporting period of October 23 through November 5, a calendar-October view contains only part of the intended purchases. Starting a November report without checking the overlap can leave late-October receipts out or cause you to select the same expense twice.

Write down the intended start and end dates before selecting the report. Compare the first and last relevant receipts with those boundaries. This small check is more reliable than assuming that every purchase visible on the current screen belongs in the submission.

Twice monthly is different from every two weeks.

Two reports each calendar month and one report every fourteen days do not describe the same schedule. If someone says “biweekly,” confirm the actual dates rather than guessing which meaning they intend. Keep their answer with your reporting instructions.

Write the confirmed schedule as actual start and end dates. If the schedule changes, ask which submission should use the new range and check for gaps or overlap with the previous one. Keep already submitted purchases identifiable when you adjust your routine.

Review the dates shown in BillBack.

BillBack organizes expenses by period or month and supports period-based PDF export. Check the displayed range before creating the file. Review amounts, merchant details and attached receipts within that range rather than relying only on the total at the top.

Use manual selection when a reporting range includes expenses that do not belong together. A client visit and unrelated office supplies may share a week but need different reports. Select the intended purchases and verify the resulting summary before sending it.

Distinguish purchase dates from later activity.

A receipt date, the date a card transaction appears and the day you entered the expense can differ. Use the date information your reviewer requires and retain the supporting receipt. If a correction changes which period an expense falls into, check whether it was included in a previous report.

For travel crossing time zones or a booking paid before departure, explain the relevant context instead of changing dates to make everything fit the trip. Your organization determines how those purchases should be reported. The app’s date range does not make the eligibility decision.

Keep period and submission records together.

Use a clear report label or file name that identifies the actual range or job, then retain the submitted version. When you follow up, refer to that specific report. This is especially helpful when several reports are awaiting review at the same time.

Princeton’s documentation guidance illustrates the need for understandable purchase context, but does not set your reporting schedule. Get that schedule from the person reviewing your expenses and use it consistently. A period is an organizing choice, not proof that payment has been scheduled.