Sourcing · Payments

About the Payments category

Sourcing › Payments payments research use only documentation quality

Pinned Wiki

KLindqvistTL4 Moderator8 Sep 2024#1

Community wiki post. Any member at trust level 3 or above can edit this post; every edit is recorded. Last edited by hana.sato on 6 Jan 2025.

26 Nov 2024 — KLindqvist: Removed a claim that the cited source did not support.
2 Oct 2024 — mira.patel: Replaced an unsourced figure with the published one and cited it.
6 Jan 2025 — hana.sato: Added the worked example and a unit label to the table header.

Editors: KLindqvist, mira.patel, hana.sato

Staff post. Actions described here are recorded in the public moderation log and may be challenged in Meta.

Payment mechanics, chargeback reality, and the recurring risks. No payment facilitation of any kind here.

This post is a community wiki: any member at trust level 3 or above can edit it, and every edit is recorded with its author and a note. If the scope described here has drifted from what actually gets posted, edit it rather than starting a topic about it.

What belongs here

Questions specific to payments, with the units and the context stated.
Reports and datasets, with the collection method stated.
Disagreement about the substance, conducted in public.

What belongs elsewhere

Anything urgent belongs in Safety, immediately, and not here.
Anything about how this site works belongs in Meta.
Requests for a maintained page belong in Wiki requests.

Before posting, it is worth checking the documentation commons and this category's tag pages. A great deal of what gets asked here has a maintained answer with a review date on it, which is more reliable than a two-year-old reply.

45 likes 23mo

hana.satoTL4 Moderator10 Oct 2024#2

Staff post. Actions described here are recorded in the public moderation log and may be challenged in Meta.

Moderation notes for this category, so that nothing about how it is run is a surprise.

Topics get moved into and out of here regularly. A move is not a judgement — the category tree is not obvious from outside and putting a question in the wrong place is expected. When I move something I say so in the topic and the action appears in the public log with the guideline cited.

The two guidelines that come up most often in this category are R2, on supplying a source when asked, and R7, on category placement. Neither is used punitively.

0 likes 22mo

s.hartmannTL22 Nov 2024#3

As a member rather than staff: the most useful thing I did when I started reading this category was to work through the tag pages rather than the topic list. The topic list shows you what is recent. The tags show you what is settled.

3 likes 21mo

KForsbergTL2Member22 Nov 2024#4

Suggestion for the wiki post above: it would be worth linking the two or three most-referenced topics in this category directly, since new members reliably ask for exactly those. Happy to make the edit myself if nobody objects, with a revision note.

11 likes 20mo

MSaarinenTL3Regular11 Dec 2024#5

KLindqvist, post #1: Payment mechanics, chargeback reality, and the recurring risks. No payment facilitation of any kind here. This post is a community wiki: any member at trust level 3 or above can edit it, and every edit is recorded with its author and a note. If the scope described here has drifted from what actually gets posted, edit it rather than… Go to post

Documentation and tax implications: payments you make for compounds might have implications for tax reporting depending on your jurisdiction. Keeping clear records matters.

The conclusion is tentative; the arithmetic underneath it is not.

32 likes in reply to #1 20mo

This topic was referenced in

Coming back to: Payment mechanics and the recovery options that do not existSourcing › Payments · 11 replies
Documenting a payment dispute without naming and shaming — the long versionSourcing › Payments · 2 replies
Coming back to: Payment method and the leverage it gives you, rankedSourcing › Payments · 26 replies

Suggested topics

Topic	Participants	Replies	Views	Activity
A payment that went through twice: how it was resolved Sourcing › Payments payments research use only documentation quality Solved Closed A payment that went through twice: how it was resolved Writing it up because I had to work it out twice and would rather nobody else did. A payments question, with the mechanics separated from the money. What…	+20	24	55k	3mo
Documenting a payment dispute without naming and shaming Sourcing › Payments documentation quality research use only payments Documenting a payment dispute without naming and shaming — setting out what I have, and where I think it stops being reliable. A payments question, with the mechanics separated from the money. What I would…	+5	9	9.8k	2mo
Payment mechanics and the recovery options that do not exist — what changed since Sourcing › Payments documentation quality payments research use only Solved On the subject in the title: Payment mechanics and the recovery options that do not exist — what changed since Working notes rather than a conclusion. A payments question, with the mechanics separated from…	+14	18	17k	13mo
Second pass at: Why chargeback is not the safety net people assume Sourcing › Payments documentation quality research use only payments Solved Second pass at: Why chargeback is not the safety net people assume Writing it up because I had to work it out twice and would rather nobody else did. Asking about the record rather than the transfer. Every…		2	25k	3mo
Second pass at: What to keep a record of at the point of payment Sourcing › Payments payments research use only documentation quality Second pass at: What to keep a record of at the point of payment — setting out what I have, and where I think it stops being reliable. A payments question, with the mechanics separated from the money. What I…	+14	18	1.9k	4mo

Related topics — sharing the tags payments, research use only, documentation quality

Topic	Participants	Replies	Views	Activity
Filing a first vendor report: a worked example Sourcing › Vendor reports third-party testing batch & lot numbers Janoshik Analytical documentation quality Filing a first vendor report: a worked example Writing it up because I had to work it out twice and would rather nobody else did. Working notes on filing a first vendor rather than a conclusion. I would…	+1	5	12k	15mo
Reconciling a label claim with a content assay Analytics › COA interpretation documentation quality amino acid analysis reference standards certificate of analysis Closed On the subject in the title: Reconciling a label claim with a content assay Working notes rather than a conclusion. The question about reconciling a label claim that I actually want answered is the second one…	+2	6	183	4mo
Documenting a supplier's response to a discrepancy Sourcing › Vendor reports third-party testing documentation quality batch & lot numbers Solved On the subject in the title: Documenting a supplier's response to a discrepancy Working notes rather than a conclusion. A question about how a record should be read rather than about a supplier. We have…	+44	49	589	8h
Coming back to: Research-use-only labelling: what it means and what it does not Sourcing › Regulatory MHRA personal import research use only Solved Research-use-only labelling: what it means and what it does not — setting out what I have, and where I think it stops being reliable. A labelling question, and I would like the answer to be about what the…	+45	50	39k	20mo
What a regulator's shortage notice actually authorises — what changed since Sourcing › Regulatory research use only EMA FDA compounding Solved The question in the title: What a regulator's shortage notice actually authorises — what changed since I will give what I have already checked below so nobody repeats it. Asking what a regulator's document…	+22	26	53k	7mo

Sponsored PeptideMeter — peptide analytics and supplier verificationPurity analysis and structured supplier verification, published as dated records rather than scores. Referenced throughout our sourcing documentation.View analytics →