Vaulting Type

Description

Credit Card / Debit Card

Credit card vault is required in order for a wallet to function. Even if there is a wallet balance, at least one card is required. The card vault charges $1.00 charge and immediately voids the charge.  The wallet owner is not charged $1.00 on their card statement.

ACH

ACH can be vaulted as a personal or business ACH. Either checking or savings can be vaulted. During the initial vault the wallet owner must sign the vaulting invoice email that is sent to them from PayJunction. There is a $0.01 charge that goes along with an initial ACH vault that is not refunded. Once an ACH is vaulted correctly, money can be transferred from the ACH account to the wallet. Each transfer will require a signature and may take a full day – or more – to settle.

Reload Setting

Description

Manual

The wallet must be loaded and replenished by the wallet owner manually. If the balance is $0 or below, the wallet owner must load the wallet with enough money to cover current and future services.

Auto Reload

The wallet owner may choose a balance threshold and a reload amount. If the wallet balance falls below the threshold, then the wallet is automatically reloaded to the wallet owner’s specified amount by way of a subsequent charge. (The wallet owner may encounter a larger charge amount than expected if the reload amount is still not enough to cover current fees.)

Pay-As-You-Go

(low- volume option)

The wallet will automatically load with enough money prior to payment. The wallet can have a zero balance (or less) – and, as soon as a request for payment via Invoice comes in, the wallet will be replenished with enough money to cover the invoice. Also note that the default payment method card will be utilized. (This is not a recommended setting for any wallet owner as it may result in many charges against the wallet owner’s default payment method. Reloading the wallet utilizing either a Manual or an Auto Reload method should always be encouraged.)

Invoice Status

Description/Meaning

Paid

Invoice has been paid by the wallet. There will be a coinciding wallet transaction that links to this invoice.

Unpaid

Invoice has not been paid. There was likely an attempt by the system to collect on this invoice and it ended up with either a low wallet balance or a card decline issue. Unpaid invoices can be attempted to be paid again by the wallet owner via the wallet. If it’s a PPR, $4 Tech or EFile Fee invoice against a return, the wallet owner can also simply attempt to re-transmit the return once the wallet issue has been resolved.

Voided

Typically, a system issue; the processing system had a problem and the invoice fell into a ‘void’ scenario. The wallet owner should try transmitting again at a later time.

Refunded

Accounting has refunded money back to the wallet from this invoice. This could be a full or partial refund. The refund will also show up in the Transactions tab.

Pending

This is not a typical status and would only display if there was an issue with the RSS collection process. Wallet owners should not worry about a ‘Pending’ status as it will either end up as ‘Paid’ (once the transaction goes through) or ‘Unpaid’ (if there is an issue charging the wallet).

Scenario

Possible Cause

Resolution

There exists an unpaid invoice for a return’s Tech or Efile Fee.

Therefore, the return has not been sent to the IRS.

The wallet did not have enough money to cover the fees after the return was transmitted …

… or, if ‘Auto Reload’ was setup, the default payment method failed to load the wallet.

Have the wallet owner load their wallet with enough money to cover fees and then click “Pay Now” on the unpaid invoice.

After clicking “Pay Now”, either the wallet will be reloaded or any credit card issues will display.

There exists an unpaid invoice for a return’s PPR fee.

Therefore, the return was never transmitted to ‘Central Site’.

The wallet did not have enough to cover the fee before the return was transmitted …

… or, if ‘Auto Reload’ was setup, the default payment method failed to load the wallet.

Have the wallet owner load their wallet with enough money to cover the fees and then have them re-transmit or re-print the 1040 return again.

There exists an unpaid invoice for one or multiple Remote Signature fees for one or multiple returns.

Therefore, the wallet owner is no longer able to send remote signatures.

The wallet did not have enough to cover the fee during the daily RSS invoicing …

… or, if ‘Auto Reload’ was setup, the default payment method failed to load the wallet.

Have the wallet owner use the “Pay Now” button on the unpaid invoice. Make sure that there are no other unpaid RSS invoices, as well.

Once they are all paid, the software will be sent an ‘unlock’ during transmit so they can resume Remote Signature functionality.

Wallet Type

Program Services Option

Description

UserID or EFIN wallet

Remote Signature Agreement

If the Account Owner has not agreed to the remote signature agreement on the portal, then the wallet owner (sub-office) can opt in from their wallet directly.

Account Level Wallet

Pay For All Charges

The account level wallet can opt to pay for all wallet charges (all services) associated with their sub-accounts’ wallets.

UserID Level Wallet (1040OL)

Pay For All Charges

The CLO user level wallet can opt to pay for all wallet charges (all services) for all of their sub-accounts’ wallets.