WH-38 vs. WH-347 on Oregon projects: one payroll, two reporting obligations

The Buildalytic workflow

Buildalytic offers Oregon certified-payroll collection and review. Its workflow offering organizes the employer/week record, reporting requirements and correction follow-up while keeping state and federal reporting routes distinct. The steps, contacts, approvals and record destinations are agreed with your team during setup.

Oregon BOLI explicitly says that completing and submitting WH-347 does not satisfy its filing requirements. Federal requirements are explained in the DOL WH-347 instructions. Determine actual project coverage with the responsible compliance professional and project documents before configuring the reporting workflow.

Sources: workflow offering; collection and follow-up

Start with obligations, not the form someone used last time

The first record should be a project reporting matrix. List the governing program, source document, reporting employer, recipient, reporting period, delivery method and responsible reviewer. Add a link to the project-specific instruction or contract clause that supports each row.

This avoids a common handoff error: the project manager says “certified payroll required,” payroll chooses its familiar export and nobody identifies a second recipient. A form name is not a complete requirement. It does not explain where to send the record, which certification applies or what evidence to keep.

If coverage is unresolved, record the question and owner. Do not configure a default as though it were an approved conclusion. Starting with an explicit open question is more useful than producing two polished reports whose applicability nobody checked.

Understand the basic distinction

BOLI describes weekly certified statements submitted to the public agency at least monthly, by the fifth business day of the following month. DOL describes weekly certified payroll submission under the federal framework. These are distinct reporting instructions, not interchangeable calendar labels.

BOLI also permits alternative reports when the requested information and certification requirements are met. DOL makes WH-347 an optional form for satisfying the federal reporting framework. “Optional form” does not mean optional reporting. Keep the chosen report format and its certification requirements together in the matrix.

These rows are a planning aid, not a replacement for the sources or the project’s actual requirements.

Keep one source record and distinct report mappings

Use approved time and payroll records as the source, then map their fields to each required output. Avoid making two independently maintained spreadsheets the source of truth. A late time correction could otherwise reach one report and miss the other.

The internal source should identify the worker, employer, work date, project, work classification, hours and the relevant payroll reference. Restrict personal and financial information to authorized staff. A project-wide coordination log can point to the restricted record without displaying worker details.

For each output, document transformations. Does the export group daily hours? Where does it show cash paid instead of benefits? How is a worker appearing under multiple classifications represented? A written crosswalk helps the reviewer distinguish an intentional formatting difference from missing information.

Reconcile the outputs before delivery

Start with the reporting period and employer. A perfectly balanced report for the wrong week is still the wrong report. Then reconcile project hours, worker entries and the relevant pay fields to the approved source.

Do not compare only the grand totals. Two mistakes can offset each other. A worker can be assigned too many hours while another has too few, leaving the report total unchanged. Use worker-level and classification-level checks appropriate to the risk and the report structure.

Keep a short explanation for every expected difference between the outputs. For example, the reports may organize the same source facts differently. The explanation should identify the field mapping. “Different form” is too vague to help a future reviewer reconstruct the decision.

A fictional dual-reporting example

Assume an authorized reviewer has determined that a fictional Oregon project has both reporting obligations. One subcontractor has three workers and 112 project hours for a week. Payroll has completed the underlying pay calculation and approved the time record.

The Oregon output and federal output each reconcile to 112 project hours. A crosswalk shows how worker classifications and benefit information appear in each. The team checks the applicable certifications and obtains the required signatures through its authorized process. It then delivers the outputs through their separately confirmed reporting routes.

The status register has two delivery records. One shows a federal submission receipt. The other shows the Oregon recipient and delivery evidence. The project stays open for reporting follow-up if either required route lacks evidence. “We sent payroll” is not used as a substitute for those two records.

If the time source later changes from 112 to 116 hours, the correction register identifies both outputs as potentially affected. The reviewer determines the required correction in each route. Neither system is treated as automatically updated because the other report was replaced.

Build a calendar that distinguishes preparation from filing

Create separate dates for source time approval, payroll review, report preparation, recipient submission and correction follow-up. An internal deadline can be earlier than an external deadline. Label it as an operating target so staff do not confuse company practice with a legal rule.

A weekly preparation rhythm can make a monthly reporting packet easier to manage. It also exposes missing weeks while the field team still remembers the work. That operational advantage does not change the official timing requirements of either program.

Make changes visible. If a subcontractor starts or finishes work midmonth, update the expected reporting periods and final-report questions. Do not keep generating missing-report alerts from a roster that nobody maintains. Conversely, a subcontractor’s last invoice does not by itself establish its final covered work period.

Make the handoff usable for the public-works team

The coordinator should be able to answer three questions without opening sensitive payroll data: what is expected, who owns the next action and what proves completion? Put those facts in the reporting register.

Reserve wage and classification review for the authorized payroll or compliance reviewer. Field supervisors can confirm work performed and hours, but that confirmation should not be silently converted into a legal determination. The workflow needs both source evidence and the right reviewer.

When a recipient requests a correction, capture its exact issue and the affected output. A generic “agency rejected payroll” note makes the subcontractor search both tracks unnecessarily. Route the request to the person who can resolve the specific discrepancy and preserve the response with the original record.

How Buildalytic handles this workflow

Use Buildalytic’s Oregon certified-payroll capability as the parent of the project’s reporting workflow, with collection and follow-up connected to the expected employer/week roster. The useful demo is a dual-route example in which a correction is traceable across both outputs.

Ask whether the reviewer can distinguish a prepared report, a signed report, a delivered report and an unresolved exception. Those states are more useful than a single completion percentage that blends all reporting tasks together.

To put this Buildalytic workflow to work, discuss the setup with your project’s source records, responsible people and expected outcome. Use the checks in this guide to verify the agreed process before rollout.

Sources: workflow offering; collection and follow-up