Righthand
← All posts

Use Stripe for an invoice collection handover

Example: A business changes the person responsible for billing follow-up. The new owner must have current invoice states and unresolved customer questions.

Keep Stripe as the source for its records. A Righthand can use available information for the decision below.

This article is from Righthand. The example and result are illustrative. This guide has no executed integration test.

The customer task

A business changes the person responsible for billing follow-up. The new owner must have current invoice states and unresolved customer questions.

Provider documentation. The documentation gives information about invoice states and invoice events. The invoice status values are draft, open, paid, uncollectible, and void.

Make account access explicit

If Stripe is available in Connections, connect the intended account. Give the Righthand access to that connection.

Provider documentation does not establish installed Righthand operations. Examine the connection’s available tools before assigning direct account work.

For direct account work, the connection must have the necessary read or write operation and permission. If that operation is unavailable, supply the information in a message. The owner must make any account change in that case.

Connection Permissions gives information about account access and tool permissions. Give only the access necessary for the identified task.

The request to the Righthand

Read the supplied invoice references.

>

Prepare current states with the related supplied customer questions.

>

Keep decisions for the new billing owner.

>

Send the owner the result before 3 PM Friday.

>

Use Pacific time.

Use the provider records for the result

Identify the exact invoice and account context. Read state and amounts together. Keep the owner's financial decisions separate from status reporting.

An open invoice does not always make the same message necessary for every customer.

For a permitted write, examine the resulting account record. A proposal does not establish a completed change.

For an external message, identify the recipient and permitted task. Ask uses an explicit instruction or approval. Connection tool permissions are another required control. Communications Policy.

An illustrative result and next step

The handover shows one paid invoice, two open invoices, and one unresolved customer question.

The new owner gives a decision about which permitted messages are necessary.

Try one account task

  1. Give the Righthand one identified source record.
  2. Compare its result with that source.
  3. Examine the account record after a permitted write.
  4. Examine the work in Activity.

If a direct operation is unavailable, give the source information in a message. This does not establish a direct integration.

When the account tools are sufficient

Use Stripe directly when its existing view gives the complete answer and no other conversation is necessary. A person can make the decision from that view.

Compare plans. Get a Righthand.