# Process Receipt File

Import a defined Receipt File in .csv format to then have Funding items populated in a response so that they can then be created or modified.  This process does not create Funding items but returns the Funding items that should be created.

Endpoint: POST /process-receipt-file
Version: v1
Security: apiKeyAuth, bearerAuth

## Header parameters:

  - `vbasoftware-database` (string, required)
    Target database

## Request fields (application/json):

  - `receipt_File_Format_Key` (integer)
    Not currently in use but in the future may allow custom import formats.  Today only the VBA standard import format is supported.

  - `receipt_File` (string,null)
    A .csv file with headers and the following columns:
- Payor_ID - REQUIRED: valid VBASoftware Payor ID
- Account_Name - REQUIRED: this is a valid VBASoftware Account name.  this must match a single FundingAccount record
- Issue_Name - REQUIRED: Issue Name on the receipt
- Issue_Type - REQUIRED: Issue Type on the receipt
- Issue_ID - REQUIRED: Issue ID on the receipt
- Funding_Type - REQUIRED: Funding Type on the receipt
- Received_Date - REQUIRED: Received Date on the receipt
- Issue_Date - REQUIRED: Issue Date on the receipt
- Issue_Amount - REQUIRED: Issue Amount  on the receipt
- Auto_Create_Deposit - Auto Create Deposit for this receipt.
- User_Name - Ignored in VBAPI, this value is overridden to the user performing the actual import
- Group_ID - Group ID for information only
- Transfer_Payor_ID - Transfer Payor ID for reference only
- Transfer_Account_Name - Transfer Account Name for reference only
- Transfer_Funding_Type - Transfer Funding Type for reference only
- Create_Check - Create Check for information only
- Expense_Type - Expense Type for reference only
- Payee_Name - Payee Name for reference only

  - `user_ID` (string,null)

## Response 200 fields (text/plain):

  - `data` (array,null)

  - `data.funding_Key` (integer, required)
    ID of the Funding record.  Note: The database will apply a default value of 0 for this field if a value is not provided.  This field is also marked as NOT NULL in the database and therefore required by the API.  If you do not have a value for this field, supply the database default value of 0 to meet the API requirements and ensure that the functionality occurs as expected.

  - `data.account_Key` (integer,null)
    ID of the funding account.

  - `data.cleared_Amount` (number,null)
    Amount that was Cleared.

  - `data.cleared_Date` (string,null)
    Date the Amount was Cleared.

  - `data.deposit_Key` (integer,null)
    ID of the Deposit.

  - `data.entry_Date` (string)
    Date record was first added to the system

  - `data.entry_User` (string,null)
    User that first added the record to the system

  - `data.funding_Status` (string,null)
    Status of the Funding.

  - `data.funding_Type` (string,null)
    Type of the Funding.

  - `data.issue_Amount` (number,null)
    Amount Issued of the Funding record.

  - `data.issue_Date` (string,null)
    Date of the Issue.

  - `data.issue_ID` (string,null)
    ID of the Issue.

  - `data.issue_Name` (string,null)
    Name of the Issue.

  - `data.issue_Type` (string,null)
    The transaction type of the Issue Amount.

  - `data.payor_ID` (string,null)
    ID of the Payor associated with the Funding record.

  - `data.received_Date` (string,null)
    Date Funding was Received.

  - `data.update_Date` (string)
    Date the record was last updated in the system

  - `data.update_User` (string,null)
    User that last updated the record in the system

  - `error` (object)

  - `error.detail` (string,null)
    A human-readable explanation specific to this occurrence of the problem.

  - `error.instance` (string,null)
    A URI reference that identifies the specific occurrence of the problem.It may
or may not yield further information if dereferenced.

  - `error.status` (integer)
    The HTTP status code([RFC7231], Section 6) generated by the origin server for
this occurrence of the problem.

  - `error.title` (string,null)
    A short, human-readable summary of the problem type.It SHOULD NOT change from
occurrence to occurrence of the problem, except for purposes of localization(e.g.,
using proactive content negotiation; see[RFC7231], Section 3.4).

  - `error.type` (string,null)
    A URI reference [RFC3986] that identifies the problem type. This specification
encourages that, when dereferenced, it provide human-readable documentation for
the problem type (e.g., using HTML [W3C.REC-html5-20141028]). When this member
is not present, its value is assumed to be "about:blank".

  - `debug` (object)

  - `debug.activityID` (string, required)


## Response 401 fields