> For the complete documentation index, see [llms.txt](https://fieldworker.gitbook.io/fieldworker-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fieldworker.gitbook.io/fieldworker-docs/fundamentals/concepts/billing.md).
# Billing
Revenue Cycle implementation in Fieldworker
## Using Fieldworker for Managing Revenue Cycle
An agency planning to use the Fieldworker platform to manage its RCM process must complete the setup described below.
1. [Subscribe](/fieldworker-docs/fundamentals/pages/settings.md#settings-subscription) to Billing in Fieldworker
2. Set up your agency [credentials](/fieldworker-docs/fundamentals/pages/settings.md#settings-agency)
3. Set up [payers](#payer)
4. Process for charge capture
1. Matching Prior Authorization to Encounters
2. Generating Claims from Encounters
5. Upload/Generate claims
6. Submit Claims
### Payer
In healthcare, a payor is a person, organization, or entity that pays for the care services administered by a healthcare provider. This term most often refers to health insurance companies, which provide customers with health plans that cover costs and reimburse for medical treatment and care services. Each time a healthcare provider submits a medical claim to a payor to receive reimbursement for a specific procedure or service, they generate information about that care episode.
Before a claim can be submitted to a payer, the payer should be defined and set up in the Fieldworker platform.
Once a payer is set up, its details are viewable on the settings page.
{% hint style="info" %}
Once a new payer is added by an agency, the system generates an email to the Fieldworker support team notifying the same and follows up on the completion of the setup with the payer.
{% endhint %}
Setting up the link with the payer is a mandatory step, generally executedsync outside the Fieldworker platform, and may take several days to complete.
## Accounts Receivable dashboard
Accounts Receivable has an estimate of all expected revenue based on the data within the Fieldworker system.
1. shows the expected receivables based on the client population and the status of their plans.
2. The entries are always up to date, so changes are automatically reflected after each change, either manually or via DDD synch
3. Prior Auth status could be manually updated to indicate if this receivable is via submission for voucher payments
4. Payment status is updated when remittance advice is received from your payers. This can also be updated manually for recording voucher payments.
5. The Billing admins can also add notes to share context about payments and/or receivables, etc.
6. The accounts receivable details for prior months may be viewed by adjusting the dates.
## Prior Auth Dashboard
The prior auth dashboard has the entries uploaded from the prior auth file. This data can not be manually updated.
1. The prior auth entries are not editable
2. The dashboard also shows the matching tasks and associated MT, if any
3. The dashboard allows the admin users to create entries for subsequent claims submission.
4. The exact matching logic is described below
1. The general expectation here is that PA entries are what you can get paid for, and if there is a matching task with an 'Approved' MT, a claim may be created.
2. There is no additional logic to auto-generate the claims from this screen
3. Are claim status, error code, and error description fields populated here?
You upload the prior auth file by clicking on the “Upload Pre-Auth CSV” in the top right of this screen (under Billing and “Charge Capture” from the side panels).
Under “Prior Authorization”, you can see any task that will need an MT to be filed. All the other information regarding the client will be pre-filled from data from the iRecord import, including the prior authorization number and service number.
## Charge capture Dashboard
The goal here is to catch the changes in the prior auth file ... for prior periods. Under “Changes Captured”, you’ll see any changes made from the previous month when uploading your pre-authorization.
1. PA file has rolling 12 months of data .. and generally has changes in the prior periods that may have happened after the last month's PA file was generated
2. among the changes identified here
1. new customer, assigned after the last PA file
2. change in plan, after the last PA file
3. customer leaving, after the last PA file
3. For all changes captured with a matching task and approved MT, a claim can be generated
4. Almost in all cases, it will be one or more partial claims to be submitted
5. Are claim status, error code, and error description fields populated here?
6. In cases where a claim may already be in place, it may need to be withdrawn
7. In some cases, there may be additional rules that may be needed when a new client is added, etc. (this may not yet be in place)
Billing claims are created through the prior authorization form you receive from the DDD at the start of every month.
To submit a claim, select the relevant claims using the checkbox, click on “Select fillable claims”, followed by “Send”.
## Claims Dashboard
1. shows the claims uploaded either via file upload or through Charge capture
2. allows adding manual claims, where needed
3. claims are run through some validations, and some fields are allowed to be edited, before EDI file generation
4. Post submission, this dashboard also shows the status and response from the billing agency, if any.
Once these claims have been filed, they’ll be displayed in the “Claims” table:
Under “Claim Status”, you’ll now see that these are “Ready to bill”, and can be submitted for billing.
## Remittances Dashboard
The remittance dashboard is one place to see all your remittances received from Medicaid, even if they have not been submitted via the Fieldworker. The data in this dashboard is populated once the weekly remittance file from Medicaid is processed.
{% file src="/files/uX5qWARQNYhs4TmcuZod" %}
